Custom Query (1145 matches)

Reported by jdreed, 15 years ago.

Moira's chsh uses /etc/shells to determine whether the user is trying to shoot themselves in the foot or not. We should either:

• add /bin/athena/tcsh and /bin/athena/bash to /etc/shells (I think we can skip cruft that's in /etc/shells on Athena 9, like shells from the gnu or sipb lockers)

• Patch chsh to use some new list (/etc/shells.moira) or something. That way we can also remove things like /sbin/nologin from the list, since on Athena 9, Moira will happily let you change your shell to that.

Reported by jdreed, 15 years ago.

/usr/athena/lib/init/login and bash_login refuse to set ZEPHYR_CLIENT if /etc/athena/dialuptype exists. I'm told that this was done on purpose because Linerva maintainers do not think users want to be running zwgc by default in X forwarded ssh sessions.

This is not a decision we should be making for users. If I log into Linerva over a tty session from somewhere, I want zwgc. I expect it to run at startup like every single other Athena machine. The message it displays is not useful for people whose .startup.tty generates a fair bit of output, as mine does (if I have more, say, 20 new mails in my INBOX, then the message about zwgc has scrolled off the screen)

We should conditionalize this on whether or not someone has "fallback = true" in .zephyr.vars. If they have set this, they expect zwgc to be running on dialups by default, and thus will not be surprised by getting multiple zephyrgrams in X forwarding SSH session. If they have not set this, then either they run zwgc -ttymode by in .startup.tty (which will still work), or they don't expect zephyr to be running by default on dialups. It's still a change from the default behavior, and should be documented, but is better than punting zwgc unconditionally.

Reported by jdreed, 15 years ago.

This ticket will collect a list of changes from Athena 9 that have not yet been documented, but should be.