[21849] in Athena Bugs
Re: Why is update_ws in /etc/athena?
daemon@ATHENA.MIT.EDU (John Hawkinson)
Fri Apr 18 05:16:34 2003
Date: Fri, 18 Apr 2003 05:16:31 -0400
From: John Hawkinson <jhawk@MIT.EDU>
To: Greg Hudson <ghudson@MIT.EDU>
Cc: bugs@MIT.EDU
Message-ID: <20030418091631.GK27037@multics.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1050646870.1552.3.camel@error-messages.mit.edu>
Do you think current situation is oK? It's infrequent to hear people
flailing trying to find update_ws.
I'm kind of skeptical on the console login thing. People run it under
X all the time and I don't think there's any widespread perception
that that is not ok...
--jhawk
Greg Hudson <ghudson@MIT.EDU> wrote on Fri, 18 Apr 2003
at 02:21:13 -0400 in <1050646870.1552.3.camel@error-messages.mit.edu>:
> update_ws belongs in /etc/athena because it's a command only executed by
> root, and that's where we put most of those commands. (Or in
> /usr/athena/etc; the distinction between the two is less interesting now
> that we don't have system packs. I note that /usr/athena/etc is in the
> default user path, but I'm not sure why.)
>
> You're only supposed to run update_ws from a console login, not from an
> su, in order to minimize bad interactions with the X server or other
> software run during a user login. Running it from a remote login is
> also okay, of course.
>
