Conversation

Notices

1. Douglas A. Whitfield (musicman@nu.federati.net)'s status on Monday, 21-Aug-2017 15:38:36 UTC Douglas A. Whitfield

   • System Administrators
   Is #sed required for ssh login in any sane system?
   • nds (nds@dent.smithfam.info)'s status on Monday, 21-Aug-2017 15:47:12 UTC nds

     in reply to
     @musicman that sounds insane
     Douglas A. Whitfield repeated this.
   • Douglas A. Whitfield (musicman@nu.federati.net)'s status on Monday, 21-Aug-2017 15:56:48 UTC Douglas A. Whitfield

     in reply to

     • nds
     Yeah, that was my thought...
     
     "First I moved the sed file from /bin to the tmp folder and restarted the instance. After this, I could not login - only access via vSphere console was possible. Move back the file, login was possible."
     
     maybe the sed is misnamed?
   • @mcscx@quitter.se (mcscx@quitter.se)'s status on Monday, 21-Aug-2017 16:16:59 UTC @mcscx@quitter.se

     in reply to
     @musicman maybe has to do with the nologin mechanism. If the admin has placed /etc/nologin users cannot log in. Maybe sed is needed for that
   • Douglas A. Whitfield (musicman@nu.federati.net)'s status on Monday, 21-Aug-2017 16:27:05 UTC Douglas A. Whitfield

     in reply to

     • @mcscx@quitter.se
     This is was I was thinking was maybe somehow sane, but it seems like the opposite would be true, but maybe if nologin set it just bombs out completely because it can't check. I wasn't able to find anything with a quick Internet search though.
   • @mcscx@quitter.se (mcscx@quitter.se)'s status on Monday, 21-Aug-2017 16:44:48 UTC @mcscx@quitter.se

     in reply to
     @musicman I'd replace /bin/sed with a script
     #!/bin/sh
     (echo SED called; date; set) >>/tmp/sed.debug 
     …
     + restart and check the file
     Douglas A. Whitfield likes this.