Your message dated Sat, 22 Aug 2009 09:28:54 +0200
with message-id <[email protected]>
and subject line Re: Bug#537394: initscripts:
/etc/rcS.d/S46mountnfs-bootclean.sh accidently delete vde2 pid files and mgmt
files in /var/run/vde2/
has caused the Debian Bug report #537394,
regarding initscripts: /etc/rcS.d/S46mountnfs-bootclean.sh accidently delete
vde2 pid files and mgmt files in /var/run/vde2/
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
537394: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=537394
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: initscripts
Version: 2.86.ds1-65
Severity: normal
Tags: patch
i have vde2 installed on my box and my /etc/network/interfaces contain
following content:
=====================
auto vde1
iface vde1 inet static
address 10.10.1.1
netmask 255.255.255.0
vde2-switch -
auto vde2
iface vde2 inet static
address 10.10.2.1
netmask 255.255.255.0
vde2-switch -
auto vde3
iface vde3 inet static
address 10.10.3.1
netmask 255.255.255.0
vde2-switch -
auto vde0
iface vde0 inet static
address 10.10.0.1
netmask 255.255.255.0
vde2-switch -
=========================
when system started, /var/run/vde2 only contain ctl dir,
drwxrws--- 6 vde2-net kvm 4096 2009-07-18 02:07 .
drwxr-xr-x 32 root root 4096 2009-07-18 02:07 ..
drwxrws--- 2 root kvm 4096 2009-07-18 02:07 vde0.ctl
drwxrws--- 2 root kvm 4096 2009-07-18 02:07 vde1.ctl
drwxrws--- 2 root kvm 4096 2009-07-18 02:07 vde2.ctl
drwxrws--- 2 root kvm 4096 2009-07-18 02:07 vde3.ctl
pid files and mgmt files are deleted by /etc/rcS.d/S46mountnfs-bootclean.sh,
and vdes cannot be used by kvm .
I've removed /etc/rcS.d/S46mountnfs-bootclean.sh , then vde2 works as expected,
folloing is the ls of /var/run/vde2:
total 40
drwxrws--- 6 vde2-net kvm 4096 2009-07-18 02:14 .
drwxr-xr-x 32 root root 4096 2009-07-18 02:16 ..
drwxrws--- 2 root kvm 4096 2009-07-18 02:33 vde0.ctl
srw-rw---- 1 root kvm 0 2009-07-18 02:14 vde0.mgmt
-rw-r--r-- 1 root kvm 5 2009-07-18 02:14 vde0.pid
drwxrws--- 2 root kvm 4096 2009-07-18 02:14 vde1.ctl
srw-rw---- 1 root kvm 0 2009-07-18 02:14 vde1.mgmt
-rw-r--r-- 1 root kvm 5 2009-07-18 02:14 vde1.pid
drwxrws--- 2 root kvm 4096 2009-07-18 02:14 vde2.ctl
srw-rw---- 1 root kvm 0 2009-07-18 02:14 vde2.mgmt
-rw-r--r-- 1 root kvm 5 2009-07-18 02:14 vde2.pid
drwxrws--- 2 root kvm 4096 2009-07-18 02:14 vde3.ctl
srw-rw---- 1 root kvm 0 2009-07-18 02:14 vde3.mgmt
-rw-r--r-- 1 root kvm 5 2009-07-18 02:14 vde3.pid
For /etc/rcS.d/S12mountall-bootclean.sh cleans /tmp , /var/lock and /var/run, I
think it is not nessary /etc/rcS.d/S46mountnfs-bootclean.sh
cleanning /tmp, /var/lock, /var/run once again, so I report this bug as a
initscripts bug
Thanks,
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.30 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages initscripts depends on:
ii debianutils 3.2 Miscellaneous utilities specific t
ii libc6 2.9-20 GNU C Library: Shared libraries
ii lsb-base 3.2-22 Linux Standard Base 3.2 init scrip
ii mount 2.15.1~rc1-1 Tools for mounting and manipulatin
ii sysvinit-utils 2.86.ds1-65 System-V-like utilities
Versions of packages initscripts recommends:
ii e2fsprogs 1.41.8-1 ext2/ext3/ext4 file system utiliti
ii psmisc 22.7-1 utilities that use the proc file s
initscripts suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.86.ds1-65
[Alan Guo]
> In you previous mail, you told me to run
> '/usr/share/insserv/check-initd-order' and 'insserv -vn', so i
> installed insserv. when installing insserv, boot orders was changed
> to current status.
Are you using unstable or testing? The reason I asked, was that your
boot sequence looked like it had been ordered using insserv before, so
I assumed these programs were available.
> for I installed upstart and other related package long long ago, and
> then I remove them, I cannot remember clearly which package I
> installed, which package change the boot sequence.
Right. Then I suspect you installed insserv some time in the past,
and tried to remove it without seeing or understanding the warning in
the debconf question stating that undo was unsafe and migth require a
reinstallation. :) The insserv migration will be one-way in the
future, and dependency based boot sequencing will be the default, so
that particular problem will go away. :)
> I'm using insserv now, It looks like fine.
Good. Because of this I close this bug as solved. :)
Happy hacking,
--
Petter Reinholdtsen
--- End Message ---
