time.google.com
time1.google.com
time2.google.com
time3.google.com
#!/usr/bin/env bash | |
# throttle-zoom '0-1' '6G' | |
set -xe | |
main() ( | |
allowedCpus="${1?Missing allowed CPUs, ex: 0-4}" | |
maxMemory="${2?Missing max memory, ex: 6G}" |
#!/usr/bin/bash -xe | |
cat <<EOF > "${HOME}/.config/systemd/user/zoom.slice" | |
[Slice] | |
AllowedCPUs=0-4 | |
MemoryHigh=6G | |
EOF | |
cat /usr/share/applications/Zoom.desktop | sed -E 's#^(Exec=).*$#Exec=/usr/bin/systemd-run --user --slice=zoom.slice /opt/zoom/ZoomLauncher#' > "${HOME}/.local/share/applications/Zoom.desktop" |
#Clone your project from git | |
composer install | |
npm install | |
copy .env.example .env | |
OR | |
cp .env.example .env | |
php artisan key:generate |
Also posted here: http://18pct.com/sending-bash-and-zsh-commands-to-syslog/
Your bash/zsh history is great if its complete, but it doesn't capture commands across all users, sudo's, root commands etc. In particular with test environments, someone may perform a "one-off" procedure and then months later it needs to be repeated. It would be nice to be able to look up what the user did at the time, and searching through multiple, possibly truncated history files is a pain.
Tools like typescript are great if you're actively documenting, but not something you would use all the time in practice and capture more than just a history of your commands. There are third-party tools like rootsh and Snoopy that can accomplish this, but third-party tools can be overkill if all you want is a quick reference in a re
"gcc: error: /usr/lib/rpm/redhat/redhat-hardened-cc1: No such file or directory" CentOS's and Fedora +22 workaround | |
Install `redhat-rpm-config` | |
$ sudo dnf install redhat-rpm-config |