Hi I have now removed the motd update code all together as it is generated at reboot anyway, so there are no use for it.
I have uploaded a version to unstable with that correction. Please test it to see if it works well for you. If it do I'll try to get it into the etch stable release if possible. Regards, // Ola On Mon, Apr 09, 2007 at 12:55:15AM +0200, Emanuele Rocca wrote: > Hello Ola, > > * Ola Lundqvist <[EMAIL PROTECTED]>, [2007-04-08 23:22 +0200]: > > On Fri, Apr 06, 2007 at 02:04:08PM +0200, Emanuele Rocca wrote: > > > [EMAIL PROTECTED]:~$ ls -l /etc/motd > > > lrwxrwxrwx 1 root root 13 2007-02-19 21:46 /etc/motd -> /var/run/motd > > > > > > [EMAIL PROTECTED]:~$ ls -l /var/lib/vservers/ns/etc/motd > > > lrwxrwxrwx 1 root root 13 2007-04-06 13:18 /var/lib/vservers/ns/etc/motd > > -> /var/run/motd > > > > > > They both point to the same file. Maybe the right thing to do is > > > creating a new motd for the guests, rather than pointing to > > > /var/run/motd? > > > > Emm yes. This is obviously a standard behaviour that must have changed > > since > > woody or something. > > > > But this must mean that this file will be regenerated at reboot, right? > > Yes, by /etc/rcS.d/S55bootmisc.sh: > > # Update motd > uname -snrvm > /var/run/motd > [ -f /etc/motd.tail ] && cat /etc/motd.tail >> /var/run/motd > > However, I do not believe that this makes the bug less important, > especially on machines that are not rebooted often like servers. > > ciao, > ema > -- --- Ola Lundqvist systemkonsult --- M Sc in IT Engineering ---- / [EMAIL PROTECTED] Annebergsslingan 37 \ | [EMAIL PROTECTED] 654 65 KARLSTAD | | http://opalsys.net/ Mobile: +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --------------------------------------------------------------- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
