- giving slices 60 seconds to start isn't realistic. Revert to previous
authorMark Huang <mlhuang@cs.princeton.edu>
Tue, 26 Oct 2004 04:45:54 +0000 (04:45 +0000)
committerMark Huang <mlhuang@cs.princeton.edu>
Tue, 26 Oct 2004 04:45:54 +0000 (04:45 +0000)
commitf64d3651d9e6789b91a08d7c8e4af4de5b2b9f0a
treefc1b363fc390d3cd6b944dbdb27be38fd76aac7b
parent03862e76d7fce9279e22b8a0ee15863041ce228e
- giving slices 60 seconds to start isn't realistic. Revert to previous
vserver-init behavior, fork off all vserver init routines (except for
high priority/system slices who can set BACKGROUND=no in their .conf
files, e.g. pl_netflow). vserver exit routines still get 60 seconds to
complete, then they are forcibly killed.
- log stdout/stderr to slice's /var/log/boot.log and close stdin for
their init routines. This may break sensitive SysV init scripts that
assume terminal access.
scripts/vserver
sysv/vservers.subst