[Pkg-sysvinit-devel] Bug#763869: sysvinit-utils: sulogin segfault after `cannot open password database!`
Dear Petter,
thank you for your reply!
I wish everyone a happy new year!
Am Freitag, den 26.12.2014, 12:34 +0100 schrieb Petter Reinholdtsen:
> [Paul Menzel]
> > Please find the updated patch below, fixing a typo in the commit message
> > and removing the note.
>
> Great. The patch need to be moved to debian/patches/, but otherwise
> look good.
Please find the updated patch below. I had hoped, that the Debian
repository is the upstream repository, to avoid using quilt for what git
does already.
> I hope someone with access to collab-maint can push a fix.
Hopefully! `git am --scissors my-message.mbox` is all which has to be
done.
> Not sure if it will make it into Jessie. It do not seem important
> enough to try to push it past the freeze.
Under certain circumstances it does not allow to get into the
maintenance shell, which is a real problem for systems still using SysV
instead of systemd I believe. systemd just tries to continue with
booting where SysV just hangs, doesn’t it?
Thanks,
Paul
8< --- >8
From f6c06a7c70f9caf376c29475578fe09993fbb9a2 Mon Sep 17 00:00:00 2001
From: Paul Menzel
Date: Tue, 16 Dec 2014 22:34:33 +0100
Subject: [PATCH] sulogin.c: Return if password database cannot be opened to
avoid crash
Currently when the maintenance console should open and the password
database cannot be opened the process `sulogin` crashes with a
segmentation fault [1].
sulogin: cannot open password database!
[3.563041] sulogin[84]: segfault at 8 ip 004018e0 sp
7fffd88d8330 error 4 in sulogin[40+3000]
Segment violation
The code calls the function `getrootpwent()` to get the root password
entry. The function should return a passwd struct and `NULL` on failure.
The return value is actually checked for `NULL` but it just prints a
message in this case and tries to continue normally, which is of course
not possible as later on the struct members are accessed.
Therefore just return 1 in case `pwd` is `NULL`.
Note: The sleep of two seconds is also questionable. Unfortunately there
is no comment explaining what the reason for it is.
Closes: #763869 (sysvinit-utils: sulogin segfault)
[1] https://bugs.debian.org/763869
---
debian/changelog | 7 +++
...ulogin_return_if_password_database_cannot_be_opened.patch | 12
debian/patches/series| 1 +
3 files changed, 20 insertions(+)
create mode 100644
debian/patches/97_sulogin_return_if_password_database_cannot_be_opened.patch
diff --git a/debian/changelog b/debian/changelog
index 4511465..9ba1a26 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+sysvinit (2.88dsf-58.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix crash when password database is not available (Closes: 763869)
+
+ -- Paul Menzel Tue, 16 Dec 2014 23:41:45
+0100
+
sysvinit (2.88dsf-58) unstable; urgency=low
* Fix typo in invoke-rc.d breaking upstart installations (Closes:
diff --git
a/debian/patches/97_sulogin_return_if_password_database_cannot_be_opened.patch
b/debian/patches/97_sulogin_return_if_password_database_cannot_be_opened.patch
new file mode 100644
index 000..3301510
--- /dev/null
+++
b/debian/patches/97_sulogin_return_if_password_database_cannot_be_opened.patch
@@ -0,0 +1,12 @@
+Index: sysvinit/src/sulogin.c
+===
+--- sysvinit.orig/src/sulogin.c
sysvinit/src/sulogin.c
+@@ -588,6 +588,7 @@ int main(int argc, char **argv)
+ if ((pwd = getrootpwent(opt_e)) == NULL) {
+ fprintf(stderr, "sulogin: cannot open password database!\n");
+ sleep(2);
++ return 1;
+ }
+ /*
+* If the root password is locked, fire up a shell
diff --git a/debian/patches/series b/debian/patches/series
index 86c824b..0d3e0c2 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -16,3 +16,4 @@
94_kfreebsd_xterm.patch
95_kfreebsd_bootlogd.patch
96_allow_multiple_console_output.patch
+97_sulogin_return_if_password_database_cannot_be_opened.patch
--
2.1.4
signature.asc
Description: This is a digitally signed message part
___
Pkg-sysvinit-devel mailing list
Pkg-sysvinit-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-sysvinit-devel
[Pkg-sysvinit-devel] Bug#763869: sysvinit-utils: sulogin segfault after `cannot open password database!`
Control: found -1 2.88dsf-58
Control: merge -1 769743 772427
Dear Debian folks,
Am Dienstag, den 16.12.2014, 23:54 +0100 schrieb Paul Menzel:
> Control: severity -1 important
> Control: tags -1 patch
I found two more bug reports for this issue and merge this report with
those.
[…]
Please find the updated patch below, fixing a typo in the commit message
and removing the note.
Thanks,
Paul
-- 8< -- >8 --
From 57d01d1992ecf78a86167b62ae88c7cb11d5bde5 Mon Sep 17 00:00:00 2001
From: Paul Menzel
Date: Tue, 16 Dec 2014 22:34:33 +0100
Subject: [PATCH] sulogin.c: Return if password database cannot be opened to
avoid crash
Currently when the maintenance console should open and the password
database cannot be opened the process `sulogin` crashes with a
segmentation fault [1].
sulogin: cannot open password database!
[3.563041] sulogin[84]: segfault at 8 ip 004018e0 sp
7fffd88d8330 error 4 in sulogin[40+3000]
Segment violation
The code calls the function `getrootpwent()` to get the root password
entry. The function should return a passwd struct and `NULL` on failure.
The return value is actually checked for `NULL` but it just prints a
message in this case and tries to continue normally, which is of course
not possible as later on the struct members are accessed.
Therefore just return 1 in case `pwd` is `NULL`.
Closes: #763869 (sysvinit-utils: sulogin segfault)
[1] https://bugs.debian.org/763869
---
debian/changelog | 7 +++
src/sulogin.c| 1 +
2 files changed, 8 insertions(+)
diff --git a/debian/changelog b/debian/changelog
index 4511465..9ba1a26 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+sysvinit (2.88dsf-58.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix crash when password database is not available (Closes: 763869)
+
+ -- Paul Menzel Tue, 16 Dec 2014 23:41:45
+0100
+
sysvinit (2.88dsf-58) unstable; urgency=low
* Fix typo in invoke-rc.d breaking upstart installations (Closes:
diff --git a/src/sulogin.c b/src/sulogin.c
index 7537654..df8907d 100644
--- a/src/sulogin.c
+++ b/src/sulogin.c
@@ -584,6 +584,7 @@ int main(int argc, char **argv)
if ((pwd = getrootpwent(opt_e)) == NULL) {
fprintf(stderr, "sulogin: cannot open password database!\n");
sleep(2);
+ return 1;
}
/*
--
2.1.4
signature.asc
Description: This is a digitally signed message part
___
Pkg-sysvinit-devel mailing list
Pkg-sysvinit-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-sysvinit-devel
[Pkg-sysvinit-devel] Bug#763869: sysvinit-utils: sulogin segfault after `cannot open password database!`
Control: severity -1 important
Control: tags -1 patch
Dear Debian folks,
Am Mittwoch, den 08.10.2014, 17:45 +0200 schrieb Axel Beckert:
> Pugachev Anatoly wrote:
> > Ahh, sorry, can't reproduce on the next boot log.
>
> But it is there. I ran into it on a freshly bootstrapped Xen DomU with
> Debian Sid and currently can reproduce it easily again and again:
>
> Begin: Loading essential drivers ... done.
> Begin: Running /scripts/init-premount ... done.
> Begin: Mounting root file system ... Begin: Running /scripts/local-top ...
> done.
> Begin: Running /scripts/local-premount ... done.
> Begin: Checking root file system ... fsck from util-linux 2.25.1
> fsck: error 2 (No such file or directory) while executing fsck.ext3 for
> /dev/xvda2
> fsck exited with status code 8
> done.
> Failure: An automatic file system check (fsck) of the root filesystem failed.
> A manual fsck must be performed, then the system restarted.
> The fsck should be performed in maintenance mode with the
> root filesystem mounted in read-only mode.
> Warning: The root filesystem is currently mounted in read-only mode.
> A maintenance shell will now be started.
> After performing system maintenance, press CONTROL-D
> to terminate the maintenance shell and restart the system.
> sulogin: cannot open password database!
> [3.563041] sulogin[84]: segfault at 8 ip 004018e0 sp
> 7fffd88d8330 error 4 in sulogin[40+3000]
> Segment violation
> Failure: Attempt to start maintenance shell failed.
> Will restart in 5 seconds.
> [8.571169] reboot: Restarting system
on one of my systems, after replacing `initramfs-tools` with `dracut`
and going back to `initramfs-tools` for some reason `fsck.ext4` is not
included in the initrd image causing the routine filesystem check to
fail. The maintenance shell does not show up though and the after the
printing of the message and the delay of two seconds the boot continues.
> There might be other things broken (which I'm hunting down currently),
> but sulogin must not segfault.
Please take a look at the patch below. I am not sure about the correct
fix. Does `return 1` make sense. Does anything check this? Should the
code continue and try to show a password prompt?
The next question is, why the root entry is not found in the database.
You can apply the patch by saving my email as an mbox file and running
`git am --scissors the/path/to/patch.mbox`.
[…]
Thanks,
Paul
-- 8< -- >8 --
From 259def1ee14e9a4fbf70d187550f8b45f92992dd Mon Sep 17 00:00:00 2001
From: Paul Menzel
Date: Tue, 16 Dec 2014 22:34:33 +0100
Subject: [PATCH] sulogin.c: Return if password database cannot be opened to
avoid crash
Currently when the maintenance console should open and the password
database cannot be opened the process `sulogin` crashes with a
segmentation fault [1].
sulogin: cannot open password database!
[3.563041] sulogin[84]: segfault at 8 ip 004018e0 sp
7fffd88d8330 error 4 in sulogin[40+3000]
Segment violation
The code calls the function `getrootpwent()` to get the root password
entry. The function should return a passwd struct and `NULL` on failure.
The return value is actually checked for `NULL` but it just prints a
message in this case and tries to continue normally, which is of course
not possible as later on the struct members are accessed.
Therefore just return 0 in case `pwd` is `NULL`.
Note: The sleep of two seconds is also questionable. Unfortunately there
is no comment explaining what the reason for it is.
Closes: #763869 (sysvinit-utils: sulogin segfault)
[1] https://bugs.debian.org/763869
---
debian/changelog | 7 +++
src/sulogin.c| 1 +
2 files changed, 8 insertions(+)
diff --git a/debian/changelog b/debian/changelog
index 4511465..9ba1a26 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+sysvinit (2.88dsf-58.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix crash when password database is not available (Closes: 763869)
+
+ -- Paul Menzel Tue, 16 Dec 2014 23:41:45
+0100
+
sysvinit (2.88dsf-58) unstable; urgency=low
* Fix typo in invoke-rc.d breaking upstart installations (Closes:
diff --git a/src/sulogin.c b/src/sulogin.c
index 7537654..d1cdebc 100644
--- a/src/sulogin.c
+++ b/src/sulogin.c
@@ -584,6 +584,7 @@ int main(int argc, char **argv)
if ((pwd = getrootpwent(opt_e)) == NULL) {
fprintf(stderr, "sulogin: cannot open password database!\n");
sleep(2);
+ return 1;
}
/*
--
2.1.3
signature.asc
Description: This is a digitally signed message part
___
Pkg-sysvinit-devel mailing list
Pkg-sysvinit-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-sysvinit-devel
[Pkg-sysvinit-devel] Bug#680293: update-rc.d manual: `update-rc.d remove name` works when `/etc/init.d/name` exists
Am Mittwoch, den 04.07.2012, 21:33 +0100 schrieb Roger Leigh: > On Wed, Jul 04, 2012 at 10:17:10PM +0200, Paul Menzel wrote: > > > > the manual of `update-rc.d` contains the following paragraph. > > > > $ man update-rc.d > > […] > > When invoked with the remove option, update-rc.d removes any > > links in the /etc/rcrunlevel.d directories to the > > script /etc/init.d/name. The script must have been deleted > > already. If the script is still present then update-rc.d aborts > > with an error message. > > […] > > This is my understanding. It should only remove the links if you use > "-f remove" to force removal. > > > It looks like `update-rc.d remove name` still works though when the > > script in `/etc/init.d/name` is not removed beforehand. > > > > $ sudo update-rc.d pulseaudio remove > > update-rc.d: using dependency based boot sequencing > > $ ls -l /etc/init.d/pulseaudio > > -rwxr-xr-x 1 root root 2227 1. Okt 2011 /etc/init.d/pulseaudio > > $ ls -l /etc/rc*.d/*audio > > ls: Zugriff auf /etc/rc*.d/*audio nicht möglich: Datei oder > > Verzeichnis nicht gefunden > > $ sudo service pulseaudio stop > > PulseAudio configured for per-user sessions ... (warning). > > > > Does the manual need updating? > > No, I think the manual is correct and update-rc.d is not behaving as > documented. I wonder though, what is the disadvantage of leaving `/etc/init.d/name` behind and `-f` has to be used to do so? > Mind you, I've not seen this before. But I can also reproduce it: > > % ls /etc/init.d/cups > /etc/init.d/cups > % ls /etc/rc*.d/*cups > /etc/rc1.d/K01cups /etc/rc2.d/S04cups /etc/rc3.d/S04cups > /etc/rc4.d/S04cups /etc/rc5.d/S04cups > % sudo update-rc.d cups remove > update-rc.d: using dependency based boot sequencing > % ls /etc/rc*.d/*cups > zsh: no matches found: /etc/rc*.d/*cups > % sudo update-rc.d cups defaults > update-rc.d: using dependency based boot sequencing > % ls /etc/rc*.d/*cups > /etc/rc1.d/K01cups /etc/rc2.d/S04cups /etc/rc3.d/S04cups > /etc/rc4.d/S04cups /etc/rc5.d/S04cups > > I'm fairly sure this didn't happen until recently. But there were only > two changes to update-rc.d in 2012, and both were trivial changes which > didn't affect this. This will need investigating in more detail. I tried it on a system with sysv-rc 2.88dsf-22.1 which has *not* been converted to dependency based boot yet. There it behaved as described in the manual. $ ls -l /etc/init.d/pulseaudio -rwxr-xr-x 1 root root 2249 Mai 18 20:54 /etc/init.d/pulseaudio $ sudo update-rc.d pulseaudio remove update-rc.d: /etc/init.d/pulseaudio exists during rc.d purge (use -f to force) > > I guess the bug has been present for a longer time, so please update the > > version information accordingly. > > > > Two more or less related notes. > > > > 1. The printing of `update-rc.d: using dependency based boot sequencing` > > is unexpected. > > It's always done this when using insserv AFAIK. If you hadn't > converted to using dependency based boot until 2.88dsf-28, this might > be new though. I used `update-rc.d` the first time, but the output looked strange to me. > I think we should remove it in wheezy+1 though, or even wheezy if it's > not going to cause too much confusion--should people who have been > converted to dependency based boot be reminded of the fact every time > update-rc.d is run? I guess the other maintainers and developers should answer that. > > 2. To disable an init.d script, is it better to just remove the > > executable flag of `/etc/init.d/name` with the latest changes in > > 2.88dsf-28? > > You can do that, certainly. Or just use "update-rc.d service disable": > > % sudo update-rc.d cups disable > update-rc.d: using dependency based boot sequencing > insserv: warning: current start runlevel(s) (empty) of script `cups' > overwrites defaults (2 3 4 5). > insserv: warning: current stop runlevel(s) (1 2 3 4 5) of script `cups' > overwrites defaults (1). > % ls /etc/rc*.d/*cups > /etc/rc1.d/K01cups /etc/rc2.d/K01cups /etc/rc3.d/K01cups > /etc/rc4.d/K01cups /etc/rc5.d/K01cups > > % sudo update-rc.d cups enable > update-rc.d: using dependency based boot sequencing > % ls /etc/rc*.d/*cups > /etc/rc1.d/K01cups /etc/rc2.d/S04cups /etc/rc3.d/S04cups > /etc/rc4.d/S04cups /etc/rc5.d/S04cups > > This converts the start links to stop links,
[Pkg-sysvinit-devel] Bug#680293: update-rc.d manual: `update-rc.d remove name` works when `/etc/init.d/name` exists
Package: sysvinit Version: 2.88dsf-28 Severity: normal Dear Debian folks, the manual of `update-rc.d` contains the following paragraph. $ man update-rc.d […] When invoked with the remove option, update-rc.d removes any links in the /etc/rcrunlevel.d directories to the script /etc/init.d/name. The script must have been deleted already. If the script is still present then update-rc.d aborts with an error message. […] It looks like `update-rc.d remove name` still works though when the script in `/etc/init.d/name` is not removed beforehand. $ sudo update-rc.d pulseaudio remove update-rc.d: using dependency based boot sequencing $ ls -l /etc/init.d/pulseaudio -rwxr-xr-x 1 root root 2227 1. Okt 2011 /etc/init.d/pulseaudio $ ls -l /etc/rc*.d/*audio ls: Zugriff auf /etc/rc*.d/*audio nicht möglich: Datei oder Verzeichnis nicht gefunden $ sudo service pulseaudio stop PulseAudio configured for per-user sessions ... (warning). Does the manual need updating? I guess the bug has been present for a longer time, so please update the version information accordingly. Two more or less related notes. 1. The printing of `update-rc.d: using dependency based boot sequencing` is unexpected. 2. To disable an init.d script, is it better to just remove the executable flag of `/etc/init.d/name` with the latest changes in 2.88dsf-28? Thanks, Paul signature.asc Description: This is a digitally signed message part ___ Pkg-sysvinit-devel mailing list Pkg-sysvinit-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-sysvinit-devel
[Pkg-sysvinit-devel] Bug#676463: #676463 sysv-rc: complains incorrectly(?) about obsolete init.d scripts for fuse and others
Am Montag, den 11.06.2012, 08:57 -0600 schrieb Gordon Haverland: […] > Manually deleting smartmontools and smartd from /etc/init.d/ and any > *smart* symlinks from /etc/rc[0-6].d/ and then doing a reinstall of > smartmontools got rid of the smartmontools problems for sysv-rc. I submitted this as #677095 [1]. Thanks, Paul [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677095 signature.asc Description: This is a digitally signed message part ___ Pkg-sysvinit-devel mailing list Pkg-sysvinit-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-sysvinit-devel
[Pkg-sysvinit-devel] Bug#676463: #676463 sysv-rc: complains incorrectly(?) about obsolete init.d scripts for fuse and others
Dear Timo, Am Montag, den 11.06.2012, 16:11 +0300 schrieb Timo Juhani Lindfors: > after changing > > add_problematic "package $package left obsolete init.d script behind" > > in /var/lib/dpkg/info/sysv-rc.postinst to > > add_problematic "package $package left obsolete init.d script $initscript > behind" > > I get nice, the suggestion worked. ;-) > ... > info: Checking if it is safe to convert to dependency based boot. > Configuring sysv-rc > --- > > Unable to migrate to dependency-based boot system > > Problems in the boot system exist which are preventing migration to > dependency-based boot sequencing: > > package fuse left obsolete init.d script /etc/init.d/fuse behind, package > initscripts left obsolete init.d script /etc/init.d/stop-bootlogd behind, > package initscripts > left obsolete init.d script /etc/init.d/bootlogd behind, package initscripts > left obsolete init.d script /etc/init.d/stop-bootlogd-single behind Please take a look at #653050 [1]. […] Thanks, Paul PS: To get the whole thread do `bts show --mbox 676463`. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653050 signature.asc Description: This is a digitally signed message part ___ Pkg-sysvinit-devel mailing list Pkg-sysvinit-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-sysvinit-devel
[Pkg-sysvinit-devel] Bug#676910: [PATCH] motd: Update usage message from `bootlogs` to `motd`
Package: initscripts Version: 2.88dsf-24 Severity: minor Tags: patch Dear Debian folks, please apply the following patch by saving this mbox file and issue `git am --scissors`. Please add the bug number to changelog file by running `git commit --amend` afterward. Thanks, Paul --- 8< >8 --- From f73fc522be61e09564c155b304a6c22e54febfca Mon Sep 17 00:00:00 2001 From: Paul Menzel Date: Sun, 10 Jun 2012 14:48:00 +0200 Subject: [PATCH] motd: Update usage message from `bootlogs` to `motd` After the split of `/etc/init.d/bootlogs` in version 2.88dsf-24 the usage message was not updated. --- debian/changelog |7 +++ debian/src/initscripts/etc/init.d/motd |2 +- 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/debian/changelog b/debian/changelog index bddf5ec..fc0ffa2 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +sysvinit (2.88dsf-27.1) UNRELEASED; urgency=low + + * Non-maintainer upload. + * Fix usage message in `/etc/init.d/motd`. + + -- Paul Menzel Sun, 10 Jun 2012 14:48:00 +0200 + sysvinit (2.88dsf-27) unstable; urgency=low [ Salvatore Bonaccorso ] diff --git a/debian/src/initscripts/etc/init.d/motd b/debian/src/initscripts/etc/init.d/motd index d636142..e0d7706 100644 --- a/debian/src/initscripts/etc/init.d/motd +++ b/debian/src/initscripts/etc/init.d/motd @@ -45,7 +45,7 @@ case "$1" in exit $? ;; *) - echo "Usage: bootlogs [start|stop|status]" >&2 + echo "Usage: motd [start|stop|status]" >&2 exit 3 ;; esac -- 1.7.10.4 signature.asc Description: This is a digitally signed message part ___ Pkg-sysvinit-devel mailing list Pkg-sysvinit-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-sysvinit-devel
[Pkg-sysvinit-devel] Bug#676463: me too and more info
Am Freitag, den 08.06.2012, 19:18 -0600 schrieb Gordon Haverland: > On June 8, 2012, Paul Menzel wrote: > > Am Freitag, den 08.06.2012, 16:34 -0600 schrieb Gordon Haverland: > > > On June 8, 2012, Paul Menzel wrote: > > > > thank for the follow up. In the future please add the > > > > addresses of all people who responded in that bug thread > > > > to CC. > > > > > > > > Even better, import the messages from the mbox you get with > > > > > > > > bts show --mbox 676463 > > > > > > What mbox? I don't get any mboxen. > > > > Did you run the command? `bts` is in package `devscripts`. > > Normally mutt opens automatically, but you can exit with `q` > > right away. The downloaded mbox (mail box) files is stored > > under > > `~/.devscripts_cache/bts/`. > > > > > I just sent an email with kmail to the bugs address for this > > > bug. > > > > I know. And I did not receive your message. I had to check the > > Web page manually to see if there was an answer. > > Sorry, I am not a developer or a Debian maintainer. I've lived > with UNIX since 1984 and computers since 1978. At heart, I am a > FORTRAN programmer, but I've dabbled in lots of stuff. I have > more than enough other stuff to keep me busy, I was just trying to > help. Downloading other mbox to add to my kmail isn't on my list > of things I want to do. It takes one minute and saves everyone else time. I cannot tell you what to do with your time. But frankly every one of us even following up on reports has »more than enough other stuff to keep her/him busy«. And most of the time it is just a matter if you take the time, which unfortunately I had to do now. By the way, if it is quicker you can also download the mbox file of one message from the »mbox« link on the HTML bug report page. To keep threading you just need the last one. > > > > and reply to the appropriate message to keep the threading > > > > and ease the life of everyone. > > > > > > I'm sure if I do that all the time, someone will come along > > > with something else I am doing wrong. > > > > Nobody has said such things to me yet. I am pretty sure that is > > the preferred way. > > Over the years, I seldom "reply to all". As a general principle, > it seemed to cause more problems than it solved. I will try to do > this with bugreports, but I suspect even there, I will find more > people wondering why I wrote them, than people thanking me for > writing them. > > > > > Am Freitag, den 08.06.2012, 21:40 +0100 schrieb Roger Leigh: > > > > > On Fri, Jun 08, 2012 at 02:16:58PM -0600, Gordon Haverland wrote: > > > > > > I have the same packages triggering init script > > > > > > warnings. > > > > > > > > > > > > In addition, I get a warning from insserv files about > > > > > > K20scsi-idle and scsi-idle missing LSB tags and > > > > > > overrides. > > > > > > > > > > Could you possibly attach a copy of each failing script? > > > > > > > > Please find the scripts attached. There seem to be also > > > > three scripts from the `initscripts` package which cause > > > > some problems. > > > > > > > > /etc/init.d > > > > /etc/init.d/rmnologin > > > > /etc/init.d/umountnfs.sh > > > > /etc/init.d/umountroot > > > > /etc/init.d/sendsigs > > > > /etc/init.d/single > > > > /etc/init.d/killprocs > > > > /etc/init.d/hostname.sh > > > > /etc/init.d/mountall.sh > > > > /etc/init.d/halt > > > > /etc/init.d/umountfs > > > > /etc/init.d/checkfs.sh > > > > /etc/init.d/mountall-bootclean.sh > > > > /etc/init.d/mountnfs.sh > > > > /etc/init.d/bootlogs > > > > /etc/init.d/mountdevsubfs.sh > > > > /etc/init.d/bootmisc.sh > > > > /etc/init.d/checkroot.sh > > > > /etc/init.d/mountnfs-bootclean.sh > > > > /etc/init.d/skeleton > > > > /etc/init.d/reboot > > > > /etc/init.d/mountoverflowtmp > > > > /etc/init.d/rc.local > > > > /etc/init.d/mtab.sh > > > > /etc/init.d/mountkernfs.sh > > > > /etc/init.
[Pkg-sysvinit-devel] Bug#653050: obsolete conffiles / symlinks not cleaned up for bootlogd split
Dear Debian folks,
Am Mittwoch, den 07.03.2012, 09:30 +0100 schrieb Michael Biebl:
> On 23.12.2011 13:11, Roger Leigh wrote:
> > On Fri, Dec 23, 2011 at 06:24:22AM +0100, Michael Biebl wrote:
> >> Package: initscripts
> >> Version: 2.88dsf-18
> >> Severity: normal
> >>
> >> Thanks for splitting bootlogd into a separate package!
> >>
> >> I noticed though, that after the upgrade I still had the obsolete
> >> conffiles installed:
> >
> > Just to clarify, was bootlogd installed at any point? If bootlogd
>
> No, I just upgraded initscripts/sysvinit-utils
> I never installed bootlogd (btw, I hope you don't add bootlogd back as a
> depends or recommends)
if I am not mistaken I also never had `bootlogd` installed.
> > gets installed, we can do conffile-related handling in the preinst,
> > but otherwise it would be rather dangerous for use to do anything
> > here, since we might remove files owned by bootlogd.
> >
> > I've moved conffiles between packages and within packages before, but
> > never kept them in the same location. That does make it trickier.
>
> This might be helpful:
>
> http://lists.debian.org/debian-devel/2012/02/msg00249.html
> http://lists.debian.org/debian-devel/2012/02/msg00254.html
> http://lists.debian.org/debian-devel/2012/02/msg00349.html
Ironically this bug leads to the problem reported in #676463 for
`sysv-rc`. (I do not know if `affects` or `blocks` have to be set.)
$ dpkg-query -W -f='${Conffiles}\n' initscripts | grep 'obsolete$'
/etc/init.d/stop-bootlogd 4544c7e1a2d0c713d29424d02faad237 obsolete
/etc/init.d/bootlogd 267ceea04f703171e6c62f506fda3305 obsolete
/etc/init.d/stop-bootlogd-single 648d8624e708151500c5e299a6005afe
obsolete
$ md5sum /etc/init.d/stop-bootlogd /etc/init.d/bootlogd
/etc/init.d/stop-bootlogd-single
4544c7e1a2d0c713d29424d02faad237 /etc/init.d/stop-bootlogd
267ceea04f703171e6c62f506fda3305 /etc/init.d/bootlogd
648d8624e708151500c5e299a6005afe /etc/init.d/stop-bootlogd-single
So `initscripts` should make sure to get these conffiles removed, if I
am not mistaken.
It would be great if you could find a solution.
Thanks,
Paul
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676463
signature.asc
Description: This is a digitally signed message part
___
Pkg-sysvinit-devel mailing list
Pkg-sysvinit-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-sysvinit-devel
[Pkg-sysvinit-devel] Bug#676463: me too and more info
Am Freitag, den 08.06.2012, 16:34 -0600 schrieb Gordon Haverland: > On June 8, 2012, Paul Menzel wrote: > > thank for the follow up. In the future please add the addresses > > of all people who responded in that bug thread to CC. > > > > Even better, import the messages from the mbox you get with > > > > bts show --mbox 676463 > > What mbox? I don't get any mboxen. Did you run the command? `bts` is in package `devscripts`. Normally mutt opens automatically, but you can exit with `q` right away. The downloaded mbox (mail box) files is stored under `~/.devscripts_cache/bts/`. > I just sent an email with kmail to the bugs address for this bug. I know. And I did not receive your message. I had to check the Web page manually to see if there was an answer. > > and reply to the appropriate message to keep the threading and > > ease the life of everyone. > > I'm sure if I do that all the time, someone will come along with > something else I am doing wrong. Nobody has said such things to me yet. I am pretty sure that is the preferred way. > > Am Freitag, den 08.06.2012, 21:40 +0100 schrieb Roger Leigh: > > > On Fri, Jun 08, 2012 at 02:16:58PM -0600, Gordon Haverland wrote: > > > > I have the same packages triggering init script warnings. > > > > > > > > In addition, I get a warning from insserv files about > > > > K20scsi-idle and scsi-idle missing LSB tags and overrides. > > > > > > Could you possibly attach a copy of each failing script? > > > > Please find the scripts attached. There seem to be also three > > scripts from the `initscripts` package which cause some > > problems. > > > > /etc/init.d > > /etc/init.d/rmnologin > > /etc/init.d/umountnfs.sh > > /etc/init.d/umountroot > > /etc/init.d/sendsigs > > /etc/init.d/single > > /etc/init.d/killprocs > > /etc/init.d/hostname.sh > > /etc/init.d/mountall.sh > > /etc/init.d/halt > > /etc/init.d/umountfs > > /etc/init.d/checkfs.sh > > /etc/init.d/mountall-bootclean.sh > > /etc/init.d/mountnfs.sh > > /etc/init.d/bootlogs > > /etc/init.d/mountdevsubfs.sh > > /etc/init.d/bootmisc.sh > > /etc/init.d/checkroot.sh > > /etc/init.d/mountnfs-bootclean.sh > > /etc/init.d/skeleton > > /etc/init.d/reboot > > /etc/init.d/mountoverflowtmp > > /etc/init.d/rc.local > > /etc/init.d/mtab.sh > > /etc/init.d/mountkernfs.sh > > /etc/init.d/urandom > > Okay, I forced dpkg to install the new initscripts package with -- > force-depends. I now get 3 mystery files from initscripts causing > problems. I also get these errors with `initscripts` 2.88dsf-22.1 installed. Only `sysv-rc` is currently not configured on this system. > I looked at all the files from initscripts that install in init.d/ > > There are 6 files which do not have a last line which starts with > a full colon. One that does has > : exit 0 > There are 6 files where the first executable line is not PATH= > There are 6 files where the first non-empty line after ### END > INIT INFO line is a comment line. > There are 5 or 6 lines in the INIT INFO area, where there is no > argument to the field, but there is whitespace after the full > colon. I believe two of the files have a tab as the trailing > whitespace, the remainder having a single space as the trailing > whitespace. I think one file has both (one of each). Interesting. Did you fix these right away (and send patches)? :P > Without knowing what your program is looking for, that is all I > can guess at. Guess we have to check what the package scripts actually check. > Time to get back to writing a presentation on NORM. Whatever NORM is, good luck with your presentation. Thanks, Paul signature.asc Description: This is a digitally signed message part ___ Pkg-sysvinit-devel mailing list Pkg-sysvinit-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-sysvinit-devel
[Pkg-sysvinit-devel] Bug#676463: me too and more info
Gordon, thank for the follow up. In the future please add the addresses of all people who responded in that bug thread to CC. Even better, import the messages from the mbox you get with bts show --mbox 676463 and reply to the appropriate message to keep the threading and ease the life of everyone. Am Freitag, den 08.06.2012, 21:40 +0100 schrieb Roger Leigh: > On Fri, Jun 08, 2012 at 02:16:58PM -0600, Gordon Haverland wrote: > > I have the same packages triggering init script warnings. > > > > In addition, I get a warning from insserv files about K20scsi-idle > > and scsi-idle missing LSB tags and overrides. > > Could you possibly attach a copy of each failing script? Please find the scripts attached. There seem to be also three scripts from the `initscripts` package which cause some problems. /etc/init.d /etc/init.d/rmnologin /etc/init.d/umountnfs.sh /etc/init.d/umountroot /etc/init.d/sendsigs /etc/init.d/single /etc/init.d/killprocs /etc/init.d/hostname.sh /etc/init.d/mountall.sh /etc/init.d/halt /etc/init.d/umountfs /etc/init.d/checkfs.sh /etc/init.d/mountall-bootclean.sh /etc/init.d/mountnfs.sh /etc/init.d/bootlogs /etc/init.d/mountdevsubfs.sh /etc/init.d/bootmisc.sh /etc/init.d/checkroot.sh /etc/init.d/mountnfs-bootclean.sh /etc/init.d/skeleton /etc/init.d/reboot /etc/init.d/mountoverflowtmp /etc/init.d/rc.local /etc/init.d/mtab.sh /etc/init.d/mountkernfs.sh /etc/init.d/urandom But I do not know which. Thanks, Paul fuse Description: application/shellscript libchipcard-tools Description: application/shellscript smartmontools Description: application/shellscript signature.asc Description: This is a digitally signed message part ___ Pkg-sysvinit-devel mailing list Pkg-sysvinit-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-sysvinit-devel
[Pkg-sysvinit-devel] Bug#676520: Bug#676463: sysv-rc: complains incorrectly(?) about obsolete init.d scripts for fuse and others
Am Donnerstag, den 07.06.2012, 18:57 +0100 schrieb Roger Leigh: > severity 676463 serious > severity 676520 serious > forcemerge 676463 676520 > thanks > > On Thu, Jun 07, 2012 at 09:09:55AM +0200, Paul Menzel wrote: > > in contrast to earlier versions, with this version installation of > > `sysv-rc` fails when migration to dependency based boot fails. > > Additionally it complains about obsolete init.d scripts of packages > > which were never a problem before and whose init.d scripts do not seem > > to be obsolete. > > Previously, sysv-rc gave you two options: legacy bootordering or > dependency based bootordering. You could keep the broken scripts > and remain with legacy, or you could clean up the scripts and > enable dependency bootordering. > > The change here is that we now require you to migrate to > dependency based bootordering, because we will no longer support > legacy static ordering. Please have a read through the details > in NEWS.Debian: > > +sysv-rc (2.88dsf-23) experimental; urgency=low > + > + Dependency based boot ordering is now required. > + > + Most systems will already be using dependency based boot ordering. > + This includes all squeeze and later releases, unless you have taken > + deliberate action to disable it. Installations upgraded from etch, > + lenny or earlier releases will have enabled dependency based booting > + when upgrading to squeeze and later releases. However, it was > + previously possible to opt out of migrating to dependency based > + booting and retain static boot ordering. This is no longer the case. > + > + If your system is still using static boot ordering, migrating to > + dependency based boot ordering will be performed when sysv-rc is > + configured. If this is not possible for any reason, you will have to > + correct the problem before upgrading can continue. It will not be > + possible to complete the upgrade until insserv is configured. > + > + The most commonly encountered problem preventing migration is the > + presence of obsolete init scripts from removed (but unpurged) > + packages. If this is the case, you will be prompted with > + instructions detailing how to purge these old packages. > + > + If you have custom init scripts, please ensure that these have the > + correct dependency information in an LSB header so that they will be > + run at the correct point in the boot sequence. > + > + -- Roger Leigh Wed, 18 Apr 2012 23:30:37 +0100 > > > sysv-rc (2.88dsf-26) wird eingerichtet ... > > info: Checking if it is safe to convert to dependency based boot. > > > > error: Unable to migrate to dependency based boot sequencing. > > error: Problems detected: package fuse left obsolete init.d script > > behind, package initscripts left obsolete init.d script behind, package > > initscripts left obsolete init.d script behind, package initscripts left > > obsolete init.d script behind, package libchipcard-tools left obsolete > > init.d script behind, package smartmontools left obsolete init.d script > > behind, , package gdm removed but not purged > > > > If this is due to the presence of unpurged obsolete initscripts, > > it is suggested that the following is run to remove them: > > dpkg --purge fuse initscripts initscripts initscripts > > libchipcard-tools smartmontools > > This is wrong; we shouldn't be purging initscripts. Could you possibly > let me know which specific files were left behind which were causing > problems? We should be able to correct this during the upgrade. > > > Also the other init.d scripts are packaged properly. > > Yes. The ones causing problems aren't current ones, they are > obsolete ones left by removed (but not purged) packages. Purging > the packages will remove them, allowing you to continue. As David pointed out in this replies too, the assumptions that the listed packages were removed is incorrect. $ LANG=C aptitude show fuse Package: fuse New: yes State: installed Automatically installed: yes Version: 2.9.0-1 Priority: optional Section: utils Maintainer: Daniel Baumann Architecture: i386 Uncompressed Size: 177 k Depends: libc6 (>= 2.4), libfuse2 (= 2.9.0-1), adduser, mount (>= 2.19.1), sed (>= 4), udev | makedev Conflicts: fuse-utils (< 2.8.5-2~) Breaks: loop-aes-utils (< 2.16.2-3~) Replaces: fuse-utils Description: Filesystem in Userspace Filesystem in Userspace (FUSE) is a simple interface for userspace programs to export a virtual filesystem to the Linux kernel.
[Pkg-sysvinit-devel] Bug#676463: sysv-rc: complains incorrectly(?) about obsolete init.d scripts for fuse and others
Package: sysv-rc Version: 2.88dsf-26 Severity: important Dear Debian folks, in contrast to earlier versions, with this version installation of `sysv-rc` fails when migration to dependency based boot fails. Additionally it complains about obsolete init.d scripts of packages which were never a problem before and whose init.d scripts do not seem to be obsolete. sysv-rc (2.88dsf-26) wird eingerichtet ... info: Checking if it is safe to convert to dependency based boot. error: Unable to migrate to dependency based boot sequencing. error: Problems detected: package fuse left obsolete init.d script behind, package initscripts left obsolete init.d script behind, package initscripts left obsolete init.d script behind, package initscripts left obsolete init.d script behind, package libchipcard-tools left obsolete init.d script behind, package smartmontools left obsolete init.d script behind, , package gdm removed but not purged If this is due to the presence of unpurged obsolete initscripts, it is suggested that the following is run to remove them: dpkg --purge fuse initscripts initscripts initscripts libchipcard-tools smartmontools See http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot for more information about dependency based boot sequencing. To reattempt the migration process run 'dpkg --configure sysv-rc'. dpkg: Fehler beim Bearbeiten von sysv-rc (--configure): Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück Fehler traten auf beim Bearbeiten von: sysv-rc This is an example for the package `fuse`. $ dpkg -S /etc/init.d/fuse fuse: /etc/init.d/fuse Also the other init.d scripts are packaged properly. Thanks, Paul -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages sysv-rc depends on: ii debconf [debconf-2.0] 1.5.43 ii insserv1.14.0-3 ii sysvinit-utils 2.88dsf-26 Versions of packages sysv-rc recommends: ii lsb-base 4.1+Debian6 Versions of packages sysv-rc suggests: pn bum pn sysv-rc-conf -- debconf information: * sysv-rc/unable-to-convert: sysv-rc/convert-legacy: true signature.asc Description: This is a digitally signed message part ___ Pkg-sysvinit-devel mailing list Pkg-sysvinit-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-sysvinit-devel
[Pkg-sysvinit-devel] Bug#546580: [update-rc.d] Provide option to permanently disable service, also after upgrade.
retitle 546580 [update-rc.d] Provide option to permanently disable service, also after upgrade. severity 546580 wishlist quit Am Montag, den 14.09.2009, 13:10 +0200 schrieb Petter Reinholdtsen: > [Paul Menzel] > > Could you add some information about this issue in the man page or > > the Debian Wiki? […] > What more did you propose to do? Sorry, that I overlooked it. I guess I am missing the word »permanently« or so to find it right away. > There is also the experimental feature in sysv-rc, to let update-rc.d > do the disabling using "update-rc.d ssh disable". The API is not yet > final, and the feature is not implemented in file-rc, so do not expect > this to keep working in the future. :) That is great. I retitled this report and set it to wishlist, so that if the disable-option is implemented this report can be closed. If you wanted to close it nevertheless beforehand, I would be fine with it too. Bests and thanks for your time, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Pkg-sysvinit-devel mailing list Pkg-sysvinit-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-sysvinit-devel
[Pkg-sysvinit-devel] Bug#546580: [update-rc.d] Permanently disable service, also after upgrade.
Subject: sysv-rc: [update-rc.d] Permanently disable service, also after upgrade. Package: sysv-rc Version: 2.87dsf-4 Severity: normal X-Debbugs-CC: debian-eeepc-de...@lists.alioth.debian.org *** Please type your report below this line *** Dear update-rc.d hackers, the following question was asked on Debian-eeepc-devel [1]. Am Sonntag, den 13.09.2009, 21:05 +0200 schrieb Jelle de Jong: […] > I disable services with the following command example: > sudo update-rc.d -f ssh remove > > But everytime the package of the init script is updated the service is > enabled again on boot. How do you all solve this? It driving me mad to > run my "disable unneeded services" script every few months? Nobody answered so far and I thought, I ask you directly instead forwarding this to debian-user. Could you add some information about this issue in the man page or the Debian Wiki? Thanks, Paul [1] http://lists.alioth.debian.org/pipermail/debian-eeepc-devel/2009-September/002570.html -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages sysv-rc depends on: ii debconf [debconf-2.0] 1.5.27 Debian configuration management sy ii insserv 1.12.0-12 Tool to organize boot sequence usi ii sysvinit-utils2.87dsf-4 System-V-like utilities Versions of packages sysv-rc recommends: ii lsb-base 3.2-23 Linux Standard Base 3.2 init scrip Versions of packages sysv-rc suggests: pn bum(no description available) pn sysv-rc-conf (no description available) -- debconf information excluded signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Pkg-sysvinit-devel mailing list Pkg-sysvinit-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-sysvinit-devel
