OpenVZ Forum


Home » General » Support » CT starts in vz init, even if stopped before and disabled. (CT starts in vz init, even if stopped before and disabled.)
CT starts in vz init, even if stopped before and disabled. [message #48713] Wed, 07 November 2012 20:15 Go to previous message
JAlbstmeijer is currently offline  JAlbstmeijer
Messages: 12
Registered: April 2006
Junior Member
Hi,


running:

2.6.32-042stab063.2
vzctl-4.1-1
vzctl-core-4.1-1


CT starts with vz init even if state was stopped and ONBOOT=no for that CT

ik looks like

vzlist -aH -octid -s-bootorder $velist

in /etc/init.d/vz returns my CT when $velist is empty


+ need_restart=
++ ls /var/lib/vzctl/vzreboot
++ awk '$2 == "yes" {print $1}'
++ vzlist -aH -octid,onboot
+ velist=
++ vzlist -aH -octid -s-bootorder
+ velist=101
+ sysctl -q -w net.ipv4.route.src_check=0
+ for veid in '$velist'
+ '[' 101 = 0 ']'
+ __echo 'Starting CT 101: '
+ '[' redhat = redhat ']'
+ echo -n 'Starting CT 101: '


Thank you.

[Updated on: Wed, 07 November 2012 21:07]

Report message to a moderator

 
Read Message
Read Message
Read Message
Previous Topic: OpenVZ via Veth with Proxmox
Next Topic: Container stall leads to server hang
Goto Forum:
  


Current Time: Fri Aug 09 23:18:02 GMT 2024

Total time taken to generate the page: 0.02976 seconds