Re: Possible boot ordering issues with the packages in Sid
Le dimanche 23 mai 2010 à 15:55 -0400, Joey Hess a écrit : > Josselin Mouette >gdm (U) > warning: script gdm/init.d/gdm possibly missing dependency on $syslog >gdm3 (U) > warning: script gdm3/init.d/gdm3 possibly missing dependency on $syslog AFAICT gdm uses its own logging system. However, PAM will log authentication requests themselves through syslog, but I don’t think we should hold the loading of gdm for that. -- .''`. Josselin Mouette : :' : `. `' “If you behave this way because you are blackmailed by someone, `-[…] I will see what I can do for you.” -- Jörg Schilling signature.asc Description: This is a digitally signed message part
Re: Possible boot ordering issues with the packages in Sid
> warning: script watchdog/init.d/watchdog possibly missing dependency on > $syslog This one's a false positive because watchdog depends on $all. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org ICQ 179140304, AIM/Yahoo/Skype michaelmeskes, Jabber mes...@jabber.org VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100524091620.ga12...@feivel.credativ.lan
Re: Possible boot ordering issues with the packages in Sid
[Christian PERRIER]
> I wonder what in keymap.sh is triggerring this. TTBOMK,
> /etc/init.d/keymap.sh is meant to work without /usr being mounted
This part of the script matches the /usr/s?bin regex:
unicode_start_stop()
{
# Switch unicode mode by checking the locale.
# This will be needed before loading the keymap.
[ -x /usr/bin/unicode_start ] || [ -x /bin/unicode_start ] || return
[ -x /usr/bin/unicode_stop ] || [ -x /bin/unicode_stop ] || return
No idea if it is a false positive or not. Note that one need to be
careful with scripts started from rcS.d/, to make sure no dependency
loop is created. Scripts that need to start before mountall.sh or
mountnfs.sh can't depend on $local_fs or $remote_fs without creating a
loop.
But then again, I believe a lot of scripts currently started in rcS.d/
should be moved out of there. :)
> samba is not using syslog by default in Debian. Still, I understand
> this might be a problem for users who want to activate logging
> through syslog. I don't really see any problem adding $syslog to
> dependencies
It is probably the best option, yeah. I believe it best to start most
services after the syslog collector, to make sure any kernel messages
generated are collected at the correct time.
Happy hacking,
--
Petter Reinholdtsen
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/2fl7hmtzrm9@login1.uio.no
Re: Possible boot ordering issues with the packages in Sid
> Christian Perrier >console-common (U) > warning: script console-common/init.d/keymap.sh possibly missing > dependency on $remote_fs I wonder what in keymap.sh is triggerring this. TTBOMK, /etc/init.d/keymap.sh is meant to work without /usr being mounted >samba (U) > error: scripts samba/init.d/samba,samba4/init.d/samba4 provide > duplicate 'samba' Error in samba4. Fixed in experimental. > warning: script samba/init.d/samba possibly missing dependency on > $syslog samba is not using syslog by default in Debian. Still, I understand this might be a problem for users who want to activate logging through syslog. I don't really see any problem adding $syslog to dependencies >samba4 (U) > error: scripts samba/init.d/samba,samba4/init.d/samba4 provide > duplicate 'samba' > warning: script samba4/init.d/samba4 possibly missing dependency on > $syslog > info: script samba4/init.d/samba4 does not provide its own name > If we fix samba, we'll fix samba4 signature.asc Description: Digital signature
Re: Possible boot ordering issues with the packages in Sid
On Sun, May 23, 2010 at 08:25:34PM +0200, Petter Reinholdtsen wrote: > warning: script ircd-irc2/init.d/ircd-irc2 possibly missing dependency on > $syslog We already covered this in #469605 and it's a false positive. Kurt -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100523201504.ga10...@roeckx.be
Re: Possible boot ordering issues with the packages in Sid
[Patrick Matthäi] > Thanks for the list, but wouldn't it be better to submit bugreports? :) Absolutely, and thank you for volunteering. I submit bug reports as quickly as I find time to review issues and report them (I have perhaps 5-10 minutes per day available for this), and as you can see from the list, more people are needed to do this in a reasonable amount of time. :) Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2flhblyzbsc@login1.uio.no
Re: Possible boot ordering issues with the packages in Sid
Am 23.05.2010 20:25, schrieb Petter Reinholdtsen: Every day, I run a archive wide consistency check of all the init.d scripts in Debian. It detect dependencies on non-existing facilities, duplicate provides and other problems. Here is the complete list from today, also available fromhttp://lintian.debian.org/~pere/>. There are quite a few false positive here. For example the missing $remote_fs check look for /usr/s?bin in the script, and will report a missing dependency also for scripts not using files in /usr/. The missing $syslog check look for a syslog symbol being mentioned in some binary in the package, and do not really know if the binary is started at boot. Anyway, sharing this with you all, in the hope that some of you might be motivated to review your packages init.d scripts to increase the quality of the init.d script dependencies. Please help me reduce the number of init.d script dependency issues. Most of these issues are not reported to BTS, as it require time to verify that the reported issue is a real problem, and I have not had time to do that for most of these packages. I know it would be better to order the list by maintainer, but have not found a simple way to do that with the format I have available. Thanks for the list, but wouldn't it be better to submit bugreports? :) -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer E-Mail: pmatth...@debian.org patr...@linux-dev.org Comment: Always if we think we are right, we were maybe wrong. */ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4bf97797.5030...@debian.org
Possible boot ordering issues with the packages in Sid
Every day, I run a archive wide consistency check of all the init.d scripts in Debian. It detect dependencies on non-existing facilities, duplicate provides and other problems. Here is the complete list from today, also available from http://lintian.debian.org/~pere/ >. There are quite a few false positive here. For example the missing $remote_fs check look for /usr/s?bin in the script, and will report a missing dependency also for scripts not using files in /usr/. The missing $syslog check look for a syslog symbol being mentioned in some binary in the package, and do not really know if the binary is started at boot. Anyway, sharing this with you all, in the hope that some of you might be motivated to review your packages init.d scripts to increase the quality of the init.d script dependencies. Please help me reduce the number of init.d script dependency issues. Most of these issues are not reported to BTS, as it require time to verify that the reported issue is a real problem, and I have not had time to do that for most of these packages. I know it would be better to order the list by maintainer, but have not found a simple way to do that with the format I have available. == 18 errors == error: script apcupsd/init.d/ups-monitor is unreadable error: script netscript-2.4-upstart/init.d/netscript is unreadable error: script netscript-2.4-upstart/init.d/netscript-interface is unreadable error: script nvidia-glx-legacy-71xx/init.d/nvidia-glx-legacy-71xx is missing LSB header error: script nvidia-glx-legacy-96xx/init.d/nvidia-glx-legacy-96xx is missing LSB header error: script powstatd/init.d/powerfail is missing LSB header error: script thin/init.d/thin is unreadable error: scripts dicod/init.d/dicod,dicod/init.d/dictd provide duplicate 'dicod' error: scripts genpower/init.d/genpower,genpower/init.d/ups-monitor provide duplicate 'genpower' error: scripts busybox-syslogd/init.d/busybox-klogd,klogd/init.d/klogd provide duplicate 'klogd' error: scripts postfix/init.d/postfix,xmail/init.d/xmail provide duplicate 'mail-transport-agent' error: scripts powstatd/init.d/powstatd,powstatd/init.d/ups-monitor provide duplicate 'powstatd' error: scripts root-system-rootd/init.d/root-system-rootd,root-system-xrootd/init.d/root-system-xrootd provide duplicate 'root-file-server' error: scripts samba/init.d/samba,samba4/init.d/samba4 provide duplicate 'samba' error: scripts busybox-syslogd/init.d/busybox-syslogd,dsyslog/init.d/dsyslog provide duplicate 'syslogd' error: script drbd8-utils/init.d/drbd do not start or stop in any runlevels error: script honeyd/init.d/honeyd do not start or stop in any runlevels error: script rabbitmq-server/init.d/rabbitmq-server do not start or stop in any runlevels == 194 warnings == warning: script ample/init.d/ample possibly missing dependency on $syslog warning: script argus-server/init.d/argus-server possibly missing dependency on $syslog warning: script asterisk/init.d/asterisk possibly missing dependency on $syslog warning: script atm-tools/init.d/atm possibly missing dependency on $syslog warning: script auditd/init.d/auditd possibly missing dependency on $syslog warning: script aumix-common/init.d/aumix relate to non-existing provides: devfsd warning: script bastille/init.d/bastille-firewall possibly missing dependency on $remote_fs warning: script blktrace/init.d/mountdebugfs possibly missing dependency on $remote_fs warning: script blktrace/init.d/mountdebugfs does not start in the usual runlevels: 1 2 3 4 5 s warning: script blootbot/init.d/blootbot relate to non-existing provides: mysql-ndb mysql-ndb-mgm warning: script boinc-client/init.d/boinc-client possibly missing dependency on $syslog warning: script c-icap/init.d/c-icap possibly missing dependency on $syslog warning: script capi4hylafax/init.d/capi4hylafax relate to non-existing provides: faxq hfaxd capiinit isdnactivecards warning: script chillispot/init.d/chillispot possibly missing dependency on $syslog warning: script chrony/init.d/chrony possibly missing dependency on $syslog warning: script clvm/init.d/clvm possibly missing dependency on $syslog warning: script cman/init.d/cman possibly missing dependency on $remote_fs warning: script cman/init.d/cman possibly missing dependency on $syslog warning: script console-common/init.d/keymap.sh possibly missing dependency on $remote_fs warning: script corosync/init.d/corosync possibly missing dependency on $syslog warning: script cryptmount/init.d/cryptmount-early possibly missing dependency on $syslog warning: script cryptsetup/init.d/cryptdisks possibly missing dependency on $remote_fs warning: script cryptsetup/init.d/cryptdisks possibly missing dependency on $syslog warning: script cryptsetup/init.d/cryptdisks-early possibly missing dependency on $remote_fs warning: script cryptsetup/init.d/cryptdisks-early possibly missing dependency on $syslog warning: script ctdb/init.d/ctdb possibly missing dependency on $syslog wa
