Thanks for the confirmation Graziano. I will add a proposal for a fix in
the new bug.
For future reference, if you find a bug affects a different package then you
thought first, you can change the package in the existing bug report. You can
do that by pressing the down arrow in the yellow bar, u
Reported to sysklogd as bug #304774
https://bugs.launchpad.net/bugs/304774
--
initscripts in jaunty does not umount root filesystem jfs
https://bugs.launchpad.net/bugs/302871
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
That made the trick for me also.
Why are klogd and syslogd not terminated anymore? Debug "feature"?
This bug is to be considered unrelated to both jfs and initscripts, and should
be reported in some way to system logging daemons devels.
Thanks to Albert for pointing this out.
Closed for me.
--
The lines "Kernel logging re-started after SIGSTOP" are strange.
I have the same messages (with / on ext3), also seeing / is busy when I
shutdown or reboot. It seems klogd and syslogd are not terminated anymore, and
keep the file system busy.
As a work-around, I have created symlinks in /etc/rc{
This is the relevant part after shutdown:
Nov 29 11:44:05 portatile init: tty4 main process (4639) killed by TERM signal
Nov 29 11:44:05 portatile init: tty5 main process (4640) killed by TERM signal
Nov 29 11:44:05 portatile init: tty2 main process (4646) killed by TERM signal
Nov 29 11:44:05 por
Can you please attach a syslog containing a shutdown sequence?
If you do it quickly after you started your system it will be in
/var/log/syslog. If you do it later the log may have rotated to
/var/log/syslog.0
** Changed in: sysvinit (Ubuntu)
Status: New => Incomplete
--
initscripts in
