Public bug reported:
I got locked out of my server via SSH, simply by extracting a tar file.
No matter how crazy it sounds, it is reproducible.
1. login as root
2. wget
https://github.com/aristocratos/btop/releases/download/v1.0.9/btop-1.0.9-linux-x86_64.tbz`
3. tar -xjvf btop-1.0.9-linux-x86_64
I feel it's important to add that the very last comment (Stanley
Sisneros (stanley-sisneros) wrote on 2018-05-30) is wrong, and the right
workaround is by Tomasz Konefal (twkonefal-j) wrote on 2018-05-07.
That is, add this to crontab:
@reboot root sleep 5 && sysctl --system
--
You received this
Actually, the line which works without specifying a PATH in a cron.d
file is the following:
@reboot root /bin/sleep 5 && /sbin/sysctl --system
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/50093
Titl
Public bug reported:
In Ubuntu 16.04, a "reboot" command does not terminate the ssh session.
This results in clients hanging, until timing out (sometimes as much as
120 seconds).
This also introduces bugs to all orchestration / automation tools which work
over SSH, since they cannot issue their
Public bug reported:
The default logrotate config uses the "syslog" group.
> # use the syslog group by default, since this is the owning group
> # of /var/log/syslog.
> su root syslog
This is not correct anymore since 16.04, because:
1. "syslog" group doesn't exist on a stock Ubuntu 16.04 syste
