cloud engineer
Here’s how to keep your SSH timeout alive for a longer period.
Edit /etc/ssh/sshd_config. Adjust interval and count max.
ClientAliveInterval 1200 ClientAliveCountMax 3 |
ClientAliveInterval 1200 ClientAliveCountMax 3
ClientAliveInterval is set to 1200 and ClientAliveCountMax is set to the default which is 3. This means unresponsive SSH clients will be disconnected after approximately 3600 seconds or 1 hour.
Here’s how to add or edit the PATH in Git Bash. Edit your bash_profile.
vi ~/.bash_profile |
vi ~/.bash_profile
Set your path by adding the new path at the end.
PATH="/c/WINDOWS/system32:/c/Users/firstname.lastname/google-cloud-sdk/bin" |
PATH="/c/WINDOWS/system32:/c/Users/firstname.lastname/google-cloud-sdk/bin"
The example path listed above is truncated for brevity.
Here’s how to display a list of application load balancers.
aws elbv2 describe-load-balancers --profile --region us-east-1 |
aws elbv2 describe-load-balancers --profile --region us-east-1
Here’s how to display classic load balancers.
aws elb describe-load-balancers --profile --region us-east-1 |
aws elb describe-load-balancers --profile --region us-east-1
I was getting an error when launching Audacity.
The error was:
“The system has detected that another copy of Audacity is running.”
However, Audacity wasn’t running at all. Not one process. It turned out to be just a locked file located in /var/tmp/audacity-[your-username].
All you have to do is delete the entire directory and rerun Audacity.
rm -rf /var/tmp/audacity=[your-username]/ |
rm -rf /var/tmp/audacity=[your-username]/
Once deleted, Audacity starts right up with no issues.
Who is accessing a particular directory? There’s a Linux command called fuser which will tell you who’s running processes in that directory.
fuser /etc/apache/ fuser /home/john/ |
fuser /etc/apache/ fuser /home/john/
Verbose.
fuser /data/exports/ -v |
fuser /data/exports/ -v
Check out the fuser man page.