On Tue, Dec 18, 2012 at 08:52:33PM +0100, Roberto Puzzanghera wrote: > Hello all, > suddenly I can't get vprocunhide enabled at boot time. I have > to run it from the command line it once the boot process is > complete. This happened when I modified my /etc/HOSTNAME. > Further modification of the HOSTNAME appears to enable or > disable vprocunhide on boot randomly. sounds strange to me ... > Any idea on the cause of this issue? no idea ATM, but I'd suspect a runlevel/init issue/bug > What can I provide to help further diagnose? I'd put a simple log or file output into the appropriate runlevel script (for vprocunhide) or wrap the vprocunhide binary with a shell wrapper to see when and how it is called, e.g. something like: echo "`date` vprocunhide called" >>/root/vprocunhide.log or logger "vprocunhide called" HTH, Herbert > regards > Roberto Puzzanghera > # vserver-info > Versions: > Kernel: 3.5.7-vs2.3.4.3-smp > VS-API: 0x00020308 > VCI: 0x0000000013000f11 > util-vserver: 0.30.216-pre3038; Dec 10 2012, 23:53:01 > Features: > CC: gcc, gcc (GCC) 4.7.1 > CPPFLAGS: '' > CFLAGS: '-g -O2 -std=c99 -Wall -pedantic -W > -funit-at-a-time' > build/host: > x86_64-unknown-linux-gnu/x86_64-unknown-linux-gnu > Use dietlibc: yes > Build C++ programs: > Build C99 programs: yes > Available APIs: v13,net,v21,v22,v23,netv2 > ext2fs Source: e2fsprogs > syscall(2) invocation: alternative > vserver(2) syscall#: 236/glibc > crypto api: beecrypt > python bindings: no > use library versioning: yes > Paths: > prefix: /usr/local > sysconf-Directory: ${prefix}/etc > cfg-Directory: ${prefix}/etc/vservers > initrd-Directory: $(sysconfdir)/init.d > pkgstate-Directory: ${prefix}/var/run/vservers > vserver-Rootdir: /vservers