On Thu, Dec 20, 2018 at 01:56:39PM +0100, andrew glaeser wrote: >Steve McIntyre <st...@einval.com> wrote: >> >> I've been bitten by this myself, so I recognise the symptoms. >> >> You've logged in and used "su" to switch to root. We've recently >> switched to using the "su" provided by the util-linux source package >> instead of the older one from shadow, and this is a consequence of >> that change. To change environment properly, you need to use "su -" >> instead. > >Well, I guess then it really is a minor issue only, I would have tried to fix >the path-variable next, bit if you have another solution it is fine for me, >even better, if you want. >Does this have to go into the release-notes anyway?
Yes, it probably should. I'm not sure if it's there already, I need to check. >Other thing, that caught my attention was, that you obviously have to wait a >few minutes upon reboot, until you can log in with SSH. Is this actually >intended to be this way: > >> andrew@a68n:~$ ssh user@detst >> ssh: connect to host detst port 22: Connection refused >> andrew@a68n:~$ ssh user@detst >> ssh: connect to host detst port 22: Connection refused >> andrew@a68n:~$ ssh user@detst >> ssh: connect to host detst port 22: Connection refused >> andrew@a68n:~$ ssh user@detst >> ssh: connect to host detst port 22: Connection refused >> andrew@a68n:~$ ssh user@detst >> ssh: connect to host detst port 22: Connection refused >> andrew@a68n:~$ ssh user@detst >> Linux detst 4.18.0-3-amd64 #1 SMP Debian 4.18.20-2 (2018-11-23) x86_64 That's a separate issue. *Maybe* a lack of entropy (see [1]), but it could be other things too. Check your logs for related messages maybe? [1] https://daniel-lange.com/archives/152-Openssh-taking-minutes-to-become-available,-booting-takes-half-an-hour-...-because-your-server-waits-for-a-few-bytes-of-randomness.html -- Steve McIntyre, Cambridge, UK. st...@einval.com "...In the UNIX world, people tend to interpret `non-technical user' as meaning someone who's only ever written one device driver." -- Daniel Pead
