Re: MOTD in g-s-d
- From: Jens Granseuer <jensgr gmx net>
- To: Rodrigo Moya <rodrigo gnome-db org>
- Cc: Control Center List <gnomecc-list gnome org>
- Subject: Re: MOTD in g-s-d
- Date: Thu, 15 Nov 2007 20:05:43 +0100
On 15.11.2007 19:43, Rodrigo Moya wrote:
On Thu, 2007-11-15 at 19:10 +0100, Jens Granseuer wrote:
> Haven't looked at the patch, but I think the comments on the bug
> are spot on: Why would you want to put a once-at-login activity
> into a long-running daemon? I don't see much of a difference between
> gnome-session and g-s-d in that respect.
>
> We have an autostart mechanism, and it should be trivial to do
> with zenity, for example.
>
right, but if the MOTD changes, that zenity-based thing wouldn't show
the changes, so you need a long-running daemon to do that. And instead
of having yet another process, we can use g-s-d.
As I said, it just does not show only the message at login time, it does
it whenever the /etc/motd file changes, which is very useful for users
in multi-user systems.
Ok, if you actually want to continually monitor the file, that makes a bit
more sense. On the other hand, that might also make it more suitable for
gnome-session again, since it's not really a setting.
And a good thing that could be added to this g-s-d module is the ability
to show messages from the console (like 'system is shutting down in 5
mins'), which wouldn't be possible with a simple zenity-based
autostarted script
In that case, you should really think about renaming it to something other
than MotD...
Jens
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]