Hi all,

is it possible to capture the output of the init process (to se what
happens on VE startup)?

- Dietmar

you can run VE /sbin/init with environment variable CONSOLE set to some file.
in this case it's output will get into file.
# man init

Thanks,
Kirill



Dietmar Maurer wrote:
> Hi all,
> 
> is it possible to capture the output of the init process (to se what
> happens on VE startup)?
> 
> - Dietmar
> 
> 
>

But I cant do that with current vzctl, instead I need to modify the
source?

env.c 301: char *envp[] = {"HOME=/", "TERM=linux",
"CONSOLE=/var/log/init.log", NULL}; 

Is that the way to do it?

- Dietmar

> you can run VE /sbin/init with environment variable CONSOLE 
> set to some file.
> in this case it's output will get into file.
> # man init

or you can replace /sbin/init with some script adding this to env
and running original init binary.

Kirill

Dietmar Maurer wrote:
> But I cant do that with current vzctl, instead I need to modify the
> source?
> 
> env.c 301: char *envp[] = {"HOME=/", "TERM=linux",
> "CONSOLE=/var/log/init.log", NULL}; 
> 
> Is that the way to do it?
> 
> - Dietmar
> 
> 
>>you can run VE /sbin/init with environment variable CONSOLE 
>>set to some file.
>>in this case it's output will get into file.
>># man init
> 
> 
>

OK, tried it both ways, but output is truncated by vzctl stop.

For example the following init script:

-----------------
#!/bin/sh

# file must be there - create it
echo >/var/log/init.log
export CONSOLE=/var/log/init.log
exec /sbin/init.org

-----------------

then I start the VE and try to view the log:

> vzctl start 777

> tail -100f /var/lib/vz/root/777/var/log/init.log
stty: standard input: Inappropriate ioctl for device
/etc/rcS.d/S03udev: line 265: echo: write error: Operation not permitted
Activating swap...done.
mount: permission denied
Cleaning up ifupdown....
....


That works quite good so far, but when I stop the VE the file gets
truncated:

tail: /var/lib/vz/root/777/var/log/init.log: file truncated

Any idea why? I already searched the sysvinit code sources, but found
nothing there.

- Dietmar

 
> or you can replace /sbin/init with some script adding this to 
> env and running original init binary.
> 
> Kirill
> 
> Dietmar Maurer wrote:
> > But I cant do that with current vzctl, instead I need to modify the 
> > source?
> > 
> > env.c 301: char *envp[] = {"HOME=/", "TERM=linux", 
> > "CONSOLE=/var/log/init.log", NULL};
> >

> tail: /var/lib/vz/root/777/var/log/init.log: file truncated
> 
> Any idea why? I already searched the sysvinit code sources, 
> but found nothing there.

'vzctl stop' does not work at all with my modified init - no processes
killed.

- Dietmar

Ah, got it - its because i need to pass correct parameters to init.

- Dietmar 

> -----Ursprüngliche Nachricht-----
> Von: users-bounces@openvz.org 
> [mailto:users-bounces@openvz.org] Im Auftrag von Dietmar Maurer
> Gesendet: Dienstag, 11. Dezember 2007 13:52
> An: users@openvz.org; Kirill Korotaev
> Betreff: RE: [Users] init output
> 
>  
> > tail: /var/lib/vz/root/777/var/log/init.log: file truncated
> > 
> > Any idea why? I already searched the sysvinit code sources, 
> but found 
> > nothing there.
> 
> 'vzctl stop' does not work at all with my modified init - no 
> processes killed.
> 
> - Dietmar
> 
>

On Tue, Dec 11, 2007 at 01:51:30PM +0100, Dietmar Maurer wrote:
>  
> > tail: /var/lib/vz/root/777/var/log/init.log: file truncated
> > 
> > Any idea why? I already searched the sysvinit code sources, 
> > but found nothing there.
> 
> 'vzctl stop' does not work at all with my modified init - no processes
> killed.

vzctl stop effectively calls 'init 0'.  Now that /sbin/init is your
script, it unconditionally truncates the log file, and then calls
/sbin/init.orig again without arguments.

To get what you want you need a slightly more elaborate script,
something like the following (untested):

#!/bin/sh

# file must be there - create it if we're pid 1
[ $$ = 1 ] && echo >/var/log/init.log
export CONSOLE=/var/log/init.log
exec /sbin/init.org "$@"


That said, I do think we need to implement some sort of serial
console-like device for VEs.  We'll see what can be done here.

Roman.

> To get what you want you need a slightly more elaborate 
> script, something like the following (untested):
> 
> #!/bin/sh
> 
> # file must be there - create it if we're pid 1 [ $$ = 1 ] && 
> echo >/var/log/init.log export CONSOLE=/var/log/init.log exec 
> /sbin/init.org "$@"
> 
> 
> That said, I do think we need to implement some sort of 
> serial console-like device for VEs.  We'll see what can be done here.

I already have a working init wrapper which uses a named pipe, and an
additional
logging process to read that named pipe and writes it into a file.

(init uses open without O_APPEND, so setting CONSOLE=filename will never
work)

Will post my script here as soon as it gets more stable.

- Dietmar