Bug#410485: ltsp-server: remote syslogging on ltsp clients is broken
On Sun, Feb 11, 2007 at 10:15:39PM -0800, [EMAIL PROTECTED] wrote: i still would like to be able to disable remote syslogging on the client side... something like this: on second thought, i think this simpler patch would suffice for an option to disable: === modified file 'debian/ltsp-client.ltsp-client-setup.init' --- debian/ltsp-client.ltsp-client-setup.init 2007-01-11 06:46:05 + +++ debian/ltsp-client.ltsp-client-setup.init 2007-02-18 06:32:33 + @@ -129,9 +129,11 @@ } configure_syslog() { -cat EOF /etc/syslog.conf +if [ -z $SYSLOG ] || [ $SYSLOG = remote ]; then +cat EOF /etc/syslog.conf *.* @${SYSLOG_HOST-$SERVER} EOF +fi } configure_fstab() { this keeps the default behavior like it is now (remote syslogging only), but makes it possible to disable remote syslogging by setting it to a non-empty value other than remote, where it will then use the the syslog.conf from the chroot, so any needed customizations can be handled there... thoughts? live well, vagrant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410485: [Pkg-ltsp-devel] Bug#410485: ltsp-server: remote syslogging on ltsp clients is broken
hi, On Sa, 2007-02-10 at 16:53 -0800, Vagrant Cascadian wrote: === modified file 'server/plugins/ltsp-build-client/Debian/000-basic-configuration' --- server/plugins/ltsp-build-client/Debian/000-basic-configuration 2007-01-11 06:53:01 + +++ server/plugins/ltsp-build-client/Debian/000-basic-configuration 2007-02-11 00:36:09 + hmm, we should find an automatic notification system of some kind, this change is included in ubuntu in server/plugins/ltsp-build-client/Ubuntu/000-basic-configuration since syslog was patched to accept /etc/ltsp/syslogd to override the default (since edgy), we install a syslogd file that enables remote logging with our ltsp-server package in this path. that doesnt give you the guarantee that syslogging is on if you use a differnt server, but for a default it makes still sense as you will fix the problem for a majority of users that just uses the package without tweaks. ciao oli signature.asc Description: This is a digitally signed message part
Bug#410485: [Pkg-ltsp-devel] Bug#410485: ltsp-server: remote syslogging on ltsp clients is broken
On Sun, Feb 11, 2007 at 12:05:02PM +0100, Oliver Grawert wrote: On Sa, 2007-02-10 at 16:53 -0800, Vagrant Cascadian wrote: === modified file 'server/plugins/ltsp-build-client/Debian/000-basic-configuration' --- server/plugins/ltsp-build-client/Debian/000-basic-configuration 2007-01-11 06:53:01 + +++ server/plugins/ltsp-build-client/Debian/000-basic-configuration 2007-02-11 00:36:09 + hmm, we should find an automatic notification system of some kind, this change is included in ubuntu in server/plugins/ltsp-build-client/Ubuntu/000-basic-configuration yes, sorry for not giving credit- i definitely stole it from the Ubuntu plugin, though it's a pretty basic idea :) since syslog was patched to accept /etc/ltsp/syslogd to override the default (since edgy), we install a syslogd file that enables remote logging with our ltsp-server package in this path. i think there is a syslog-ng that allows for dropping files into a directory, rather than patching to include a specific file... might be worth exploring further... that doesnt give you the guarantee that syslogging is on if you use a differnt server, but for a default it makes still sense as you will fix the problem for a majority of users that just uses the package without tweaks. yeah, sounds good overall. i still would like to be able to disable remote syslogging on the client side... something like this: === modified file 'debian/ltsp-client.ltsp-client-setup.init' --- debian/ltsp-client.ltsp-client-setup.init 2007-01-11 06:46:05 + +++ debian/ltsp-client.ltsp-client-setup.init 2007-02-12 05:49:07 + @@ -129,9 +129,15 @@ } configure_syslog() { -cat EOF /etc/syslog.conf +if [ true = $SYSLOG ]; then +cat EOF /etc/syslog.conf *.* @${SYSLOG_HOST-$SERVER} EOF +else +cat EOF /etc/syslog.conf +*.* /var/log/syslog +EOF +fi } configure_fstab() { or simply leaving the default /etc/syslog.conf in place, though it would waste a bit more ram (as default syslog duplicates some information in several files), but it would also make it possible to make customizations... live well, vagrant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410485: ltsp-server: remote syslogging on ltsp clients is broken
Package: ltsp-server Version: 0.99debian11 Severity: important Tags: patch sysklogd and klogd are not in the whitelist of services to be run by ltsp clients at boot, so they are disabled. yet ltsp clients are configured to do remote syslogging by default, but because syslogd isn't running, nothing gets logged to the servers. this is a feature used in many ltsp environments... simply adding sysklogd and klogd to the whitelist of services in runlevel 2 should fix this problem: === modified file 'server/plugins/ltsp-build-client/Debian/000-basic-configuration' --- server/plugins/ltsp-build-client/Debian/000-basic-configuration 2007-01-11 06:53:01 + +++ server/plugins/ltsp-build-client/Debian/000-basic-configuration 2007-02-11 00:36:09 + @@ -8,6 +8,6 @@ EARLY_PACKAGES=${EARLY_PACKAGES:-xorg ltsp-client discover1 mdetect xresprobe udev xdebconfigurator esound debian-archive-keyring} EXCLUDE=${EXCLUDE:-libpcap0.7,libgnutls11,liblockfile1,libpcre3,libtasn1-2,libopencdk8,liblzo1,info,manpages,man-db,libgcrypt11,libgdbm3,libgpg-error0,groff-base,at,cron,logrotate,exim4-config,exim4,exim4-base,exim4-daemon-light,ipchains,mailx,pppconfig,pppoe,pppoeconf,tasksel,base-config,apt-utils,dhcp-client,fdutils,iptables,ppp,whiptail} RCS_WHITELIST=${RCS_WHITELIST:-mountkernfs.sh mountvirtfs hostname.sh keymap.sh loopback udev mountdevsubfs.sh mountdevsubfs module-init-tools procps.sh etc-setserial ltsp-client-setup setserial console-screen.sh xorg-common x11-common xfree86-common ifupdown networking} -RC2_WHITELIST=${RC2_WHITELIST:-ltsp-client nbd-client usplash rmnologin} +RC2_WHITELIST=${RC2_WHITELIST:-klogd sysklogd ltsp-client nbd-client usplash rmnologin} ;; esac might also be worth considering a patch to disable remote syslogging, for environments where this is not desired... live well, vagrant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]