[Bug 611996] New: after reboot: recovering journal
http://bugzilla.novell.com/show_bug.cgi?id=611996 http://bugzilla.novell.com/show_bug.cgi?id=611996#c0 Summary: after reboot: recovering journal Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: koenig@linux.de QAContact: qa@suse.de Found By: --- Blocker: --- quite often after (clean?!) reboot I get "recovering journal" for the rootfs. # df -T Filesystem Type 1K-blocks Used Available Use% Mounted on /dev/sda2 ext3 20641788 4005120 15588028 21% / devtmpfs devtmpfs 505176 460 504716 1% /dev tmpfs tmpfs 510924 4 510920 1% /dev/shm /dev/sda3 ext3 169576700 309680 160652968 1% /home # fdisk -l Disk /dev/sda: 200.0 GB, 200049647616 bytes 255 heads, 63 sectors/track, 24321 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x0009110e Device Boot Start End Blocks Id System /dev/sda1 1 262 2104483+ 82 Linux swap / Solaris /dev/sda2 * 263 2873 20972857+ 83 Linux /dev/sda3 2874 24321 172281060 83 Linux from boot.omsg and boot.msg: --- 8< ------ 8< ------ 8< ------ 8< ------ 8< ------ 8< ------ 8< ------ 8< ------ 8< --- Kernel logging (ksyslog) stopped. Kernel log daemon terminating. Boot logging started on /dev/char/../tty1(/dev/console) at Sun Jun 6 15:37:32 2010 Trying manual resume from /dev/disk/by-id/ata-ST3200822AS_5LJ0C1A7-part1 Invoking userspace resume from /dev/disk/by-id/ata-ST3200822AS_5LJ0C1A7-part1 resume: libgcrypt version: 1.4.4 Trying manual resume from /dev/disk/by-id/ata-ST3200822AS_5LJ0C1A7-part1 Invoking in-kernel resume from /dev/disk/by-id/ata-ST3200822AS_5LJ0C1A7-part1 Waiting for device /dev/disk/by-id/ata-ST3200822AS_5LJ0C1A7-part2 to appear: ok fsck from util-linux-ng 2.17.2 [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a -C0 /dev/sda2 /dev/sda2: recovering journal /dev/sda2: Clearing orphaned inode 886598 (uid=0, gid=0, mode=0100600, size=217016) /dev/sda2: Clearing orphaned inode 615866 (uid=0, gid=0, mode=0100755, size=131400) /dev/sda2: Clearing orphaned inode 544725 (uid=0, gid=0, mode=0100755, size=106096) /dev/sda2: Clearing orphaned inode 544723 (uid=0, gid=0, mode=0100755, size=39952) /dev/sda2: Clearing orphaned inode 541798 (uid=0, gid=0, mode=0100755, size=265864) /dev/sda2: Clearing orphaned inode 541751 (uid=0, gid=0, mode=0100755, size=149975) /dev/sda2: Clearing orphaned inode 541736 (uid=0, gid=0, mode=0100755, size=1670408) /dev/sda2: Clearing orphaned inode 541899 (uid=0, gid=0, mode=0100755, size=108252) /dev/sda2: Clearing orphaned inode 541922 (uid=0, gid=0, mode=0100755, size=42889) /dev/sda2: Clearing orphaned inode 541961 (uid=0, gid=0, mode=0100755, size=61747) /dev/sda2: Clearing orphaned inode 543838 (uid=0, gid=0, mode=0100755, size=52494) /dev/sda2: Clearing orphaned inode 541834 (uid=0, gid=0, mode=0100755, size=135934) /dev/sda2: Clearing orphaned inode 544479 (uid=0, gid=0, mode=0100755, size=47294) /dev/sda2: clean, 147044/1313280 files, 1083196/5242880 blocks fsck succeeded. Mounting root device read-write. Mounting root /dev/disk/by-id/ata-ST3200822AS_5LJ0C1A7-part2 mount -o rw,acl,user_xattr -t ext3 /dev/disk/by-id/ata-ST3200822AS_5LJ0C1A7-part2 /root Boot logging started on /dev/char/../tty1(/dev/console) at Sun Jun 6 15:37:47 2010 --- 8< ------ 8< ------ 8< ------ 8< ------ 8< ------ 8< ------ 8< ------ 8< ------ 8< --- Kernel logging (ksyslog) stopped. Kernel log daemon terminating. Boot logging started on /dev/char/../tty1(/dev/console) at Sun Jun 6 16:10:01 2010 Trying manual resume from /dev/disk/by-id/ata-ST3200822AS_5LJ0C1A7-part1 Invoking userspace resume from /dev/disk/by-id/ata-ST3200822AS_5LJ0C1A7-part1 resume: libgcrypt version: 1.4.4 Trying manual resume from /dev/disk/by-id/ata-ST3200822AS_5LJ0C1A7-part1 Invoking in-kernel resume from /dev/disk/by-id/ata-ST3200822AS_5LJ0C1A7-part1 Waiting for device /dev/disk/by-id/ata-ST3200822AS_5LJ0C1A7-part2 to appear: ok fsck from util-linux-ng 2.17.2 [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a -C0 /dev/sda2 /dev/sda2: recovering journal /dev/sda2: Clearing orphaned inode 886599 (uid=0, gid=0, mode=0100600, size=217016) /dev/sda2: clean, 147063/1313280 files, 1083469/5242880 blocks fsck succeeded. Mounting root device read-write. Mounting root /dev/disk/by-id/ata-ST3200822AS_5LJ0C1A7-part2 mount -o rw,acl,user_xattr -t ext3 /dev/disk/by-id/ata-ST3200822AS_5LJ0C1A7-part2 /root Boot logging started on /dev/char/../tty1(/dev/console) at Sun Jun 6 16:10:09 2010 --- 8< ------ 8< ------ 8< ------ 8< ------ 8< ------ 8< ------ 8< ------ 8< ------ 8< --- -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=611996 http://bugzilla.novell.com/show_bug.cgi?id=611996#c1 Jon Nelson <jnelson-suse@jamponi.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jnelson-suse@jamponi.net --- Comment #1 from Jon Nelson <jnelson-suse@jamponi.net> 2010-07-13 19:32:26 UTC --- I'm getting this too, although I can't yet find a pattern for it. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=611996 http://bugzilla.novell.com/show_bug.cgi?id=611996#c3 Dr. Werner Fink <werner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |jack@novell.com, | |werner@novell.com Component|Basesystem |Kernel InfoProvider| |jack@novell.com AssignedTo|werner@novell.com |kernel-maintainers@forge.pr | |ovo.novell.com --- Comment #3 from Dr. Werner Fink <werner@novell.com> 2010-07-15 07:24:19 UTC --- This seems to be a kernel problem ... or a problem of the file systems tools (unlikly but ...) waht do you think Jan? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=611996 http://bugzilla.novell.com/show_bug.cgi?id=611996#c4 Jan Kara <jack@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|jack@novell.com | --- Comment #4 from Jan Kara <jack@novell.com> 2010-07-15 07:36:24 UTC --- To me it seems as if some program(s) was still running during shutdown having some deleted files open. Then ext3 fails to remount the (root) filesystem read-only (because we have to delete these deleted but open files when a file is closed) and thus the filesystem is not clean on the next boot. A way how to track this down would be to run lsof(8) just before we try to remount the root filesystem read only and store the output somewhere. When we see the problem on the next boot, we can inspect the output and see which process had open and deleted files and then think how we could fix that (e.g. by making sure the process terminates before shutdown). -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=611996 http://bugzilla.novell.com/show_bug.cgi?id=611996#c5 Dr. Werner Fink <werner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |kasievers@novell.com, | |mmarek@novell.com, | |mszeredi@novell.com InfoProvider| |koenig@linux.de --- Comment #5 from Dr. Werner Fink <werner@novell.com> 2010-07-15 07:52:41 UTC --- Hmmm ... the last few commands before remounting root ro include the line killall5 -9 .. but this command omits a few commands accessing fuse file systems then /sbin/udevd and /sbin/mdmon system deamons. Those tools should not have open a file with write access on the root file system. Harald? Please could you add a lines lsof / > /var/log/root.lsof sync before the line mount -no remount,ro / 2> /dev/null in /etc/init.d/halt and attach the resulting /var/log/root.lsof (I'm assuming that /var and /var/log belongs to your root file system:) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=611996 http://bugzilla.novell.com/show_bug.cgi?id=611996#c6 --- Comment #6 from Harald Koenig <koenig@linux.de> 2010-07-15 09:54:36 UTC --- (In reply to comment #5)
(I'm assuming that /var and /var/log belongs to your root file system:)
correct assumption: # df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda2 20641788 4196792 15396356 22% / devtmpfs 509484 460 509024 1% /dev tmpfs 510928 4 510924 1% /dev/shm /dev/sda3 169576700 337140 160625508 1% /home
Harald? Please could you add a lines
lsof / > /var/log/root.lsof sync
before the line
mount -no remount,ro / 2> /dev/null
in /etc/init.d/halt and attach the resulting /var/log/root.lsof
attached... boot.msg after reboot does not explicitly show that the journal got read (this is only visible on the console screen:( but the time stamps suggest that it did happen again for this reboot (can only check the console output in late evening tonight...). full root.lsof will be attached... this one might cause the problem ?! rc 4990 root DEL REG 8,2 886616 /var/run/nscd/passwd -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=611996 http://bugzilla.novell.com/show_bug.cgi?id=611996#c7 Harald Koenig <koenig@linux.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|koenig@linux.de | --- Comment #7 from Harald Koenig <koenig@linux.de> 2010-07-15 09:55:49 UTC --- Created an attachment (id=376106) --> (http://bugzilla.novell.com/attachment.cgi?id=376106) root.lsof -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=611996 http://bugzilla.novell.com/show_bug.cgi?id=611996#c Dr. Werner Fink <werner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #376106|application/octet-stream |text/plain mime type| | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=611996 http://bugzilla.novell.com/show_bug.cgi?id=611996#c8 Dr. Werner Fink <werner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |pbaudis@novell.com Component|Kernel |Basesystem InfoProvider| |koenig@linux.de AssignedTo|kernel-maintainers@forge.pr |bnc-team-screening@forge.pr |ovo.novell.com |ovo.novell.com --- Comment #8 from Dr. Werner Fink <werner@novell.com> 2010-07-15 10:13:54 UTC --- Hmmmm ... the /var/run/nscd/passwd is marked as deleted but it seem not happened here. Question: does a line fsync /var/run/nscd/passwd 2>/dev/null before the lsof command help? Just added Petr as maintainer of nscd to carbon copy list. I'd like to know if we may add the above line to the stop part of the boot/runlevel script of nscd/unscd. Beside this there seems to be a second problem with nscd/unscd, compare with bug #597621 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=611996 http://bugzilla.novell.com/show_bug.cgi?id=611996#c Dr. Werner Fink <werner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |pbaudis@novell.com |ovo.novell.com | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=611996 http://bugzilla.novell.com/show_bug.cgi?id=611996#c9 --- Comment #9 from Harald Koenig <koenig@linux.de> 2010-07-15 17:23:05 UTC --- (In reply to comment #8)
Hmmmm ... the /var/run/nscd/passwd is marked as deleted but it seem not happened here. Question: does a line
fsync /var/run/nscd/passwd 2>/dev/null
before the lsof command help?
tried it (without 2>/dev/null for fast eyes;), but this does not help, (as expected, see below). /var/log/root.lsof again shows rc 5892 root DEL REG 8,2 886616 /var/run/nscd/passwd and dmesg again shows a ~7 seconds which likely is the time for ext4 journal rollback: [ 5.182026] PM: Resume from disk failed. [ 12.091046] kjournald starting. Commit interval 15 seconds [ 12.091210] EXT3-fs (sda2): using internal journal [ 12.091218] EXT3-fs (sda2): mounted filesystem with ordered data mode [ 13.868606] preloadtrace: systemtap: 1.1/0.147, base: ffffffffa0220000, memory: 37data/40text/12ctx/13net/396alloc kb, probes: 44 for trying to fsync(1) a deleted file, try: sleep 999 > /tmp/SLEEP & sleep 1 lsof -p `pidof sleep` | grep SLEEP fsync /tmp/SLEEP rm /tmp/SLEEP lsof -p `pidof sleep` | grep SLEEP fsync /tmp/SLEEP with this output for the final fsync: Usage: fsync file /tmp/SLEEP: No such file or directory this does not perfectly match the /var/run/nscd/passwd example as rc uses map (see the FD column in lsof output showing "DEL" instead of a fd number!) but it shows that without existing directory entry for that file fsync(1) won't work... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=611996 http://bugzilla.novell.com/show_bug.cgi?id=611996#c Harald Koenig <koenig@linux.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|koenig@linux.de | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=611996 http://bugzilla.novell.com/show_bug.cgi?id=611996#c10 --- Comment #10 from Harald Koenig <koenig@linux.de> 2010-07-15 21:02:59 UTC --- I wondered which "bash operation" in rc script might trigger that nscd/passwd mapping... on my 11.3 test with that problem every shell shows the mapped passwd file: $ grep /var /proc/$$/maps 7f798b91f000-7f798b954000 r--s 00000000 08:02 886619 /var/run/nscd/passwd BUT on my notebook running 11.3 too I never see that mapped file! the difference (IMHO) : on the PC with problems nscd-2.11.2-2.4.x86_64 got installed, while the notebook with no fsck problems AFAIK "unscd" is installed instead: # rpm -q nscd unscd package nscd is not installed unscd-0.45-5.1.x86_64 libnscd-2.0.2-113.1.x86_64 is installed on both systems... so a workaround would be to replace nscd by unscd -- so let's try it: # zypper in unscd Loading repository data... Reading installed packages... Resolving package dependencies... Problem: unscd-0.45-5.1.x86_64 conflicts with nscd provided by nscd-2.11.2-2.4.x86_64 Solution 1: deinstallation of nscd-2.11.2-2.4.x86_64 Solution 2: do not install unscd-0.45-5.1.x86_64 Choose from above solutions by number or cancel [1/2/c] (c): 1 Resolving dependencies... Resolving package dependencies... The following NEW package is going to be installed: unscd The following package is going to be REMOVED: nscd 1 new package to install, 1 to remove. Overall download size: 30.0 KiB. After the operation, 72.0 KiB will be freed. Continue? [y/n/?] (y): Removing nscd-2.11.2-2.4 [done] Retrieving package unscd-0.45-5.1.x86_64 (1/1), 30.0 KiB (63.0 KiB unpacked) Retrieving: unscd-0.45-5.1.x86_64.rpm [done] Installing: unscd-0.45-5.1 [done] and after "rcnscd restart" a new shell does not map the passwd file anymore: # grep /var/ /proc/$$/maps 7fbe87a9b000-7fbe87ad0000 r--s 00000000 08:02 886619 /var/run/nscd/passwd # bash # grep /var/ /proc/$$/maps # et voila the time stamps after reboot for mounting the rootfs -- no delay for journal rollback anymore: [ 5.457701] kjournald starting. Commit interval 15 seconds [ 5.457880] EXT3-fs (sda2): using internal journal [ 5.457887] EXT3-fs (sda2): mounted filesystem with ordered data mode [ 7.069658] preloadtrace: systemtap: 1.1/0.147, base: ffffffffa0220000, memory: 37data/40text/12ctx/13net/396alloc kb, probes: 44 [ 8.514217] udev: starting version 157 is there any drawback when using unscd instead of nscd ? at least on my notebook I did not realize that there is an "u"nscd so far ;-) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=611996 http://bugzilla.novell.com/show_bug.cgi?id=611996#c11 --- Comment #11 from Harald Koenig <koenig@linux.de> 2010-07-16 09:02:11 UTC --- (In reply to comment #10)
is there any drawback when using unscd instead of nscd ?
just FYI: yes, there is! please have a look at bug #622910 where unscd does not start anymore/at all... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=611996 http://bugzilla.novell.com/show_bug.cgi?id=611996#c12 --- Comment #12 from Dr. Werner Fink <werner@novell.com> 2010-07-16 16:33:22 UTC --- The only explanation is that glibc will use the cache even is nscd is gone (/etc/nscd.conf -> /etc/nsswitch.conf) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=611996 https://bugzilla.novell.com/show_bug.cgi?id=611996#c13 Joerg Steffens <joerg.steffens@dass-it.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |joerg.steffens@dass-it.de --- Comment #13 from Joerg Steffens <joerg.steffens@dass-it.de> 2010-11-10 15:46:41 UTC --- same problem on openSUSE 11.2 and nscd-2.10.1-10.5.1.i586. as a workaround, I added following line to /etc/fstab: tmpfs /var/run/nscd tmpfs defaults 0 2 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=611996 https://bugzilla.novell.com/show_bug.cgi?id=611996#c14 --- Comment #14 from Joerg Steffens <joerg.steffens@dass-it.de> 2010-11-11 09:50:09 UTC --- unfortunally, using tmpfs for /var/run/nscd did not solve the problem in all cases. I'll check what other files may cause this problem on my systems next week. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=611996 https://bugzilla.novell.com/show_bug.cgi?id=611996#c15 --- Comment #15 from Joerg Steffens <joerg.steffens@dass-it.de> 2010-11-17 16:52:59 UTC --- in my case, it has been a custom daemon, that did not stop correctly. So, problem solved my openSUSE 11.2 environment. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=611996 https://bugzilla.novell.com/show_bug.cgi?id=611996#c zj jia <zjjia@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zjjia@novell.com AssignedTo|bnc-team-screening@forge.pr |matz@novell.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=611996 https://bugzilla.novell.com/show_bug.cgi?id=611996#c17 Michael Matz <matz@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|matz@novell.com |werner@novell.com Severity|Major |Critical --- Comment #17 from Michael Matz <matz@novell.com> 2011-07-12 11:57:14 UTC --- Yes, as soon as nscd (not unscd) and an application uses any of those services it will have this (or similar files for other maps) mmaped. That is by design. The only way for having these files not be mapped anymore is to stop nscd and restart the applications. Hence, what you'd need to do is split the remount-readonly step into two steps: part1.sh: killall5 -15 # at this point nscd should be gone already, due to the services being # stopped and the killalls sync exec part2.sh part2.sh mount -no remount,ro / The exec replaces the current shell (that still has /var/run/nscd/passwd mmapped) with a new one that hasn't anymore. Or we can ignore this strangeness. unscd is supposed to fully replace nscd in the future (or an even more advanced daemon), so that might not be the worst option. Werner decides. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=611996 https://bugzilla.novell.com/show_bug.cgi?id=611996#c18 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WONTFIX --- Comment #18 from Dr. Werner Fink <werner@suse.com> 2011-11-11 12:15:02 UTC --- As the rc is the master resource script /etc/init.d/rc I'd like to ignore this as re-exec of /etc/init.d/rc becomes complicated. Now with systemd and unscd this problem should be gone. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com