- revert crap (restarting will cause wrong context to be applied and limits should...

Changed files:
    util-vserver-initpost.sh -> 1.4

diff --git a/util-vserver-initpost.sh b/util-vserver-initpost.sh
index 3ead2090022f637915afbe13f25a72d12174c6d0..bb78a979d59b20b5c9be8780e82799b6016d5a9b 100644 (file)
--- a/util-vserver-initpost.sh
+++ b/util-vserver-initpost.sh
@@ -41,16 +41,13 @@ pushd "$cfgdir" &>/dev/null
 popd >/dev/null
 
 pushd "$vdir" &>/dev/null
+       if [ -f etc/sysconfig/rpm ]; then
+               subst etc/sysconfig/rpm 's!^#RPM_SKIP_AUTO_RESTART=.*!RPM_SKIP_AUTO_RESTART=yes!'
+       fi
+
        # for future. right now SysVinit is not created at build stage
        if [ -f etc/inittab ]; then
                # disable mingetty respawn
                subst etc/inittab 's!^\([^#].*:respawn:.* tty\)!#\1!'
        fi
-
-       # pam_limits causes problems
-       # http://linux-vserver.org/Frequently_Asked_Questions#When_using_nice_and_su_.28for_example.2C_in_the_updatedb_cron_job.29.2C_I_get:_su:_Permission_denied._What_does_it_mean.3F
-       for file in /etc/pam.d/*; do
-               subst ${file} 's!^\([^#].*pam_limits.so\)!#\1!'
-       done
-
 popd >/dev/null