Your message dated Sat, 16 Apr 2011 16:08:33 +0000
with message-id <[email protected]>
and subject line Bug#607136: fixed in sysvinit 2.88dsf-13.3
has caused the Debian Bug report #607136,
regarding initscripts: mountkernfs.sh: illegal handling of _non_-virtual
filesystems (RAMRUN mode), leading to multiple daemon startup failure
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.)
--
607136: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607136
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: initscripts
Version: 2.86.ds1-61
I kept wondering why openvpn failed on each bootup attempt every couple of
weeks.
Now I know that this is because mountkernfs.sh illegally attempts to
additionally handle RAMRUN mode:
# Mount /var/run and /var/lock as tmpfs if enabled
if [ yes = "$RAMRUN" ] ; then
RUN_OPT=
[ "${RUN_SIZE:=$TMPFS_SIZE}" ] && RUN_OPT=",size=$RUN_SIZE"
domount tmpfs "" /var/run varrun -omode=0755,nosuid$RUN_OPT
touch /var/run/.ramfs
fi
if [ yes = "$RAMLOCK" ] ; then
LOCK_OPT=
[ "${LOCK_SIZE:=$TMPFS_SIZE}" ] && LOCK_OPT=",size=$LOCK_SIZE"
domount tmpfs "" /var/lock varlock
-omode=1777,nodev,noexec,nosuid$LOCK_OPT
touch /var/lock/.ramfs
fi
IMHO mountkernfs.sh is so early in bootup stage that it shouldn't
have any business dealing with _any_ directory components which are non-virtual.
Probably someone misplaced this RAMRUN stuff since he thought that RAMRUN is a
virtual
fs (tmpfs), however the intent of mountkernfs.sh IMHO is not so much about the
_type_
of file system that is being processed, but about the _destination_ of the mount
(namely, being fully virtual on a _root_-partition-based mount point).
In my case of a flash-based server I have a mount that I have /var as a
_symlink_ pointing to
(yes, I know, bad dog, no cookies).
However I'd say simply deciding to mount /var as an extra partition
(a fully legal and often-implemented way) is entirely equivalent to my symlink
HACK,
since both methods would make /var available at the same time during bootup.
And that's simply not at that point in time when mountkernfs.sh RAMRUN parts
already attempt to do their tweaking.
mountkernfs.sh very early --> no /var tree (mount or directory) available -->
RAMRUN tmpfs mount fails
--> usual persistent /var/run directory will appear somewhat later
--> /var/run cleanup will get skipped by mountall-bootclean.sh due to simple
RAMRUN=true check
--> stale PID files left in /var/run --> FUBAR
Conclusion: RAMRUN parts should not get handled at dangerously early
mountkernfs.sh stage due to
/var tree involvement.
Or RAMRUN would have to state a "fixed /var tree" requirement - but in such a
case
the mountall-bootclean.sh /var/run cleanup check should not be done simply
based on
having RAMRUN set to true, but instead on whether it's _actually_ tmpfs-based
or not.
Thanks,
Andreas Mohr
--- End Message ---
--- Begin Message ---
Source: sysvinit
Source-Version: 2.88dsf-13.3
We believe that the bug you reported is fixed in the latest version of
sysvinit, which is due to be installed in the Debian FTP archive:
initscripts_2.88dsf-13.3_amd64.deb
to main/s/sysvinit/initscripts_2.88dsf-13.3_amd64.deb
sysv-rc_2.88dsf-13.3_all.deb
to main/s/sysvinit/sysv-rc_2.88dsf-13.3_all.deb
sysvinit-utils_2.88dsf-13.3_amd64.deb
to main/s/sysvinit/sysvinit-utils_2.88dsf-13.3_amd64.deb
sysvinit_2.88dsf-13.3.diff.gz
to main/s/sysvinit/sysvinit_2.88dsf-13.3.diff.gz
sysvinit_2.88dsf-13.3.dsc
to main/s/sysvinit/sysvinit_2.88dsf-13.3.dsc
sysvinit_2.88dsf-13.3_amd64.deb
to main/s/sysvinit/sysvinit_2.88dsf-13.3_amd64.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Roger Leigh <[email protected]> (supplier of updated sysvinit package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
Format: 1.8
Date: Sat, 16 Apr 2011 01:17:29 +0100
Source: sysvinit
Binary: sysvinit sysvinit-utils sysv-rc initscripts
Architecture: source amd64 all
Version: 2.88dsf-13.3
Distribution: experimental
Urgency: low
Maintainer: Debian sysvinit maintainers
<[email protected]>
Changed-By: Roger Leigh <[email protected]>
Description:
initscripts - scripts for initializing and shutting down the system
sysv-rc - System-V-like runlevel change mechanism
sysvinit - System-V-like init utilities
sysvinit-utils - System-V-like utilities
Closes: 186892 353943 378776 406685 423405 481546 483643 503805 530582 564635
585543 599241 599734 607136 612594 616571 620191 620735
Changes:
sysvinit (2.88dsf-13.3) experimental; urgency=low
.
[ Roger Leigh ]
* Non-maintainer upload.
* Support for new top-level directory /run to replace /var/run,
/var/lock, /dev/shm and /lib/init/rw as a place to store transient
writable data which should not be preserved across a system
reboot (Closes: #186892, #616571, #620191). /run fixes existing
issues with RAMRUN and RAMLOCK options using tmpfs on /var/run and
/var/lock (Closes: #423405, #481546, #564635, #607136, #620735).
Additionally, /run/shm replaces /dev/shm and may share the same
tmpfs as /run if RAMSHM is set to "no" in /etc/default/rcS. /tmp
may also be configured to be a tmpfs if RAMTMP is set to "yes" in
/etc/default/rcS. /tmp may also be configured to use /run directly if
it is symlinked to /run/tmp, for example.
Summary:
/var/run → /run
/var/lock → /run/lock
/dev/shm → /run/shm
/lib/init/rw → /run (not transitioned automatically)
/dev/.* → /run (not transitioned automatically)
These changes do not take effect until the system is rebooted as
is currently done for /lib/init/rw setup. Prior to a reboot, the
paths are made available via bind/nullfs/firmlink mounts, depending on
the platform. Following a reboot, the old paths will be converted to
symlinks, or bind/nullfs/firmlink mounts where symlinking is not
possible, to allow access via either the old or new paths, to permit
programs using the old paths to transition to use the new paths for
wheezy.
- debian/initscripts.postinst:
Take chroot detection logic from udev postinst (existing logic was
broken). Add detection logic for vserver environments and Hurd.
Trigger reboot to complete transition.
If the system has not yet transitioned to a tmpfs-based /run, set up
bind mounts as follows:
/var/run → /run
/var/lock → /run/lock
/dev/shm → /run/shm
On reboot, the system will complete the migration to a tmpfs-based
/run; this creates the directory heierachy from the old paths to
enable the use of the new /run paths prior to a restart. This means
packages may transition to using /run with a versioned dependency
upon initscripts.
Remove special handling for RAMRUN and RAMLOCK, which is now taken
care of by /run.
If in a chroot environment, just create symlinks from the new names
to the existing locations, since otherwise the changes would be
lost, and since rcS scripts aren't run the transition won't
complete.
- debian/src/initscripts/Makefile:
Provide top-level /run.
- debian/src/initscripts/doc/README.Debian:
Document new use of RUN_SIZE and LOCK_SIZE.
Document use of /run rather than /lib/init/rw.
Document use of SHM_SIZE and TMP_SIZE.
- debian/src/initscripts/etc/init.d/checkroot.sh:
Use /run in place of /lib/init/rw.
- debian/src/initscripts/etc/default/tmpfs:
Document TMPFS_SIZE, RUN_SIZE and LOCK_SIZE (Closes: #483643).
Document TMP_SIZE and SHM_SIZE.
- debian/src/initscripts/etc/init.d/mountkernfs.sh:
Create /run, /run/sendsigs.omit.d and /run/lock.
Mount /run/lock as a separate tmpfs if RAMLOCK=yes.
/run/lock has 01777 permissions to match /var/lock.
Mount /tmp as a separate tmpfs if RAMTMP=yes or / is being mounted
read-only (Closes: #503805, #585543).
Drop mounting of /var/run and /var/lock.
- debian/src/initscripts/etc/init.d/mountdevsubfs.sh:
Create /run/shm. Mount /run/shm as a separate tmpfs if RAMSHM=yes.
- debian/src/initscripts/etc/init.d/mtab.sh:
domtab mirrors behaviour of domount in mount-functions exactly, to
prevent duplicate mounts (required for bind mount support).
Bind mount /run/init and drop mounting of /var/run. Mount /run/lock
in place of /var/lock.
Mount /tmp if RAMTMP=yes.
Mount /run/shm if RAMSHM=yes.
- debian/src/initscripts/etc/init.d/sendsigs:
Use new paths:
files: /run/sendsigs.omit /lib/init/rw/sendsigs.omit
dirs: /run/sendsigs.omit.d/ /lib/init/rw/sendsigs.omit.d/
- debian/src/initscripts/etc/init.d/umountfs:
Ignore /run. Continue to ignore /lib/init/rw in order to handle
clean shutdown. No longer ignore /var/run and /var/lock.
- debian/src/initscripts/etc/init.d/umountnfs.sh:
Check for presence of .ramfs than configuration variable when
skipping /var/run and /var/lock.
Ignore /run. Continue to ignore /lib/init/rw in order to handle
clean shutdown. No longer ignore /var/run and /var/lock.
- debian/src/initscripts/lib/init/bootclean.sh
Don't clean /var/run and /var/lock (Closes: #378776). Because
these directories are now a tmpfs, cleaning no longer makes sense.
- debian/src/initscripts/lib/init/tmpfs.sh:
Read /etc/default/tmpfs and provide defaults if unset.
- debian/src/initscripts/lib/init/mount-functions.sh:
Support bind mounts in domount() (Closes: #353943).
Drop support for mounting /var/run and /var/lock as separate
tmpfs filesystems. Symlink /var/run to /run and /var/lock to
/run/lock if possible. If /var/run and /var/lock are directories,
attempt to remove and symlink if successful, or else bind mount.
- debian/src/initscripts/lib/init/vars.sh:
Read /etc/default/rcS and provide defaults if unset.
- debian/src/initscripts/man/rcS.5:
Drop documentation of RAMRUN.
Update documentation for RAMLOCK (Closes: #406685).
Document RAMTMP and RAMSHM.
- debian/src/initscripts/share/default.rcS:
Remove RAMRUN.
Add RAMSHM and RAMTMP.
RAMLOCK, RAMSHM and RAMTMP default to enabled for new installs.
.
[ Michael Biebl ]
* Remove dead usplash support code (Closes: #599241, #599734, #612594).
.
[ Martin F. Krafft ]
* Add comments to /etc/default/rcS (Closes: #530582).
.
[ Samuel Thibault ]
Hurd portability for initscripts postinst and init scripts.
Hurd does not currently support tmpfs mounts, but will do in the
future. Use firmlinks in place of bind mounts.
Checksums-Sha1:
be9d988363ea206734abf37e28aa05c0e6562b4e 1532 sysvinit_2.88dsf-13.3.dsc
de3efda313a5c2f31d54eadeeff76b161da65156 172561 sysvinit_2.88dsf-13.3.diff.gz
b78268833a44e50f9cd3e2f9c973e586e1950092 123172 sysvinit_2.88dsf-13.3_amd64.deb
124dd7d5976ab932b12836aa034285adf38ebadc 123756
sysvinit-utils_2.88dsf-13.3_amd64.deb
549bda85e582e268f0c845f510af1f15c0a78e23 75664
initscripts_2.88dsf-13.3_amd64.deb
b2825862ee97b31ff274955be71a231546dd7c83 76464 sysv-rc_2.88dsf-13.3_all.deb
Checksums-Sha256:
07d58ffae680f2875127b9192a7e2d9e4ac5d43df44592d5c353992e869352a6 1532
sysvinit_2.88dsf-13.3.dsc
661a477552f9be1a0f1f112b392a0f18f6007ca5490fc94079c771f90671cfcf 172561
sysvinit_2.88dsf-13.3.diff.gz
4c1472aef05058062225daddf11d4390824a73b7bdea886508b26b1f6722495f 123172
sysvinit_2.88dsf-13.3_amd64.deb
7990833fcea2c8b52bf91f7e2dfce748ec285270926aa2f86ffc3dcf8e9881fd 123756
sysvinit-utils_2.88dsf-13.3_amd64.deb
5f9af575d548648a96c07412df3c4a83fde14575b3cc714b16203211736795b2 75664
initscripts_2.88dsf-13.3_amd64.deb
dd1393d8206bb5b320d42f92b100636108396edb59fb993a69823aea04cae57a 76464
sysv-rc_2.88dsf-13.3_all.deb
Files:
ce5a50face05beafa6cab9642a0bb95a 1532 admin required sysvinit_2.88dsf-13.3.dsc
6dbe29e91350698e63857ae24de5ffbf 172561 admin required
sysvinit_2.88dsf-13.3.diff.gz
7518abcfd4f81b48129b56d32e0ae9a8 123172 admin required
sysvinit_2.88dsf-13.3_amd64.deb
9a672f235a3a1cae9b0435ee3397c41c 123756 admin required
sysvinit-utils_2.88dsf-13.3_amd64.deb
281d99c48bda7dd1abf32b74c5f91ab2 75664 admin required
initscripts_2.88dsf-13.3_amd64.deb
c802c38a538c6e39e05b6d079833e4f9 76464 admin required
sysv-rc_2.88dsf-13.3_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iEYEAREDAAYFAk2puNAACgkQVcFcaSW/uEgMKwCg7OelUXpt8gjS5XCQJ6fdnL8N
cvMAniD5GrfZsHPB8tn1OIkv3OQNnDoB
=KEGe
-----END PGP SIGNATURE-----
--- End Message ---
_______________________________________________
Pkg-sysvinit-devel mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/pkg-sysvinit-devel
