As I recall, if screen has utmp support and can write utmp, it will remove your login session from utmp, since screen will now multiplex all of your other session windows over that one tty, and it doesn't necessarily make sense to leave that no-longer-unique tty as your "current login."
The deflogin setting controls the default state of each screen window you create subsequently. It sounds like, for your case, you either want no utmp support at all, or you just want one window of your many windows marked as logged in. (The latter was how I mainly ran screen through most of college; since then, my "logged in" state hasn't mattered much, if at all, since nobody at work uses 'write', 'talk', 'ytalk', 'w' or 'who'.) -- We sell Spatulas, and that's all! http://spatula-city.org/~im14u2c/ http://sdk-1600.spatula-city.org/ http://spacepatrol.info/ ________________________________ From: Aaron Davies <aaron.dav...@gmail.com> To: Screen Users <screen-users@gnu.org> Sent: Fri, June 14, 2013 9:11:11 PM Subject: screen removes utmp entry for parent login? if i leave deflogin at its default setting, start screen, and create a second screen, i see two entries for myself in "who" or "w". this seems reasonable. if i set "deflogin off" in my .screenrc, start screen, and create a second screen, i see no entries at all for myself in "who" or "w". is screen removing the entry corresponding to my original login, its parent process? how do i prevent this? -- Aaron Davies aaron.dav...@gmail.com _______________________________________________ screen-users mailing list screen-users@gnu.org https://lists.gnu.org/mailman/listinfo/screen-users
_______________________________________________ screen-users mailing list screen-users@gnu.org https://lists.gnu.org/mailman/listinfo/screen-users
