edubuntu-bugs team mailing list archive

Thread
Date

[Bug 521055] Re: rsyslog is updated too late

To: edubuntu-bugs@xxxxxxxxxxxxxxxxxxx
From: müzso <bit2@xxxxxxxxxxx>
Date: Tue, 15 Feb 2011 13:21:33 -0000
Reply-to: Bug 521055 <521055@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

Confirmed on Maverick too. :-(
For now (as a workaround) we can add the otherwise dynamically created ltsp.conf to the /etc/rsyslog.d directory in the chroot and rebuild the chroot image. Of course this does not allow for per client configuration of remote syslogging (ie. in the /srv/tftp/..../lts.conf file), but probably only a handful LTSP admins would want to do that.

Imho the ideal fix would be to have a custom (LTSP) script executed
during the execution of the upstart job (/etc/init/rsyslog.conf) that
would create this /etc/rsyslog.d/ltsp.conf file if the LTSP
configuration (lts.conf) requires it.

-- 
You received this bug notification because you are a member of Edubuntu
Bugsquad, which is subscribed to ltsp in ubuntu.
https://bugs.launchpad.net/bugs/521055

Title:
  rsyslog is updated too late