1113264419 Q * albeiro Ping timeout: 480 seconds 1113264432 J * albeiro albeiro@linux.gentoo.pl 1113265342 J * kevinp ~kevinp@209.33.223.103 1113265392 M * kevinp Bertl, so I'm confused on the difference between sysv and init based, isn't sysv init based? 1113265469 M * mugwump SysV init-style is /etc/init.d, /etc/rcN.d, etc 1113265475 M * mugwump BSD init-style is /etc/rc 1113265501 M * mugwump people abuse the terms left right and centre :) 1113265540 M * kevinp hmm, so the latest vserver by default is BSD init-style, but can also be configured to use sysv-init style? 1113265554 M * Bertl yeah, and in addition to that ... here init and sysv means 1113265571 M * Bertl init = start an actual init (minit, plain) 1113265583 M * Bertl sysv = just execute the rc scripts ... 1113265618 M * kevinp so if all of my users are used to red hat servers, then I should be going with sysv? 1113265673 M * kevinp So that there would be chkconfig and the /etc/init.d and /etc/rcN.d/ folders 1113265693 M * kevinp Or can you still have that if you start it with init? 1113265708 M * Bertl yep, init is just _another_ process run inside the vserver doing that 1113265727 M * Bertl makes sense if you want to change the runlevel inside for example 1113265786 M * Bertl there is no special magic involved there ... 1113265802 M * Bertl usually when you boot a linux system, the kernel starts 1113265812 M * Bertl only one process (specified by init=) 1113265836 M * Bertl this process in turn cares about all details (like stating the runlevel scripts) 1113265870 M * Bertl but you do not need that init with linux-vservers, you can start the runlevel scripts 'by hand' 1113265962 M * kevinp So let me see if I understand this then 1113265995 M * kevinp On my current servers, the start process was starting each rc script for the vserver 1113266031 M * Bertl well, yes, actually just one rc script, which in turn started the services 1113266033 M * kevinp On the new server I have setup, the start script, starts init, which then in turn, inside the vserver, starts the other scripts 1113266047 M * Bertl yes, precisely 1113266090 M * kevinp So, if I needed to check that a particular service started, it should be in the logs of the vserver 1113266127 M * Bertl yes, as far as init logging is done ... 1113266154 M * kevinp So, now that I understand that correctly, which one do you recommend again? 1113266187 M * Bertl depends on your usage pattern ... 1113266221 M * kevinp Well, I would think that most users would not need to change their runlevels except for rebooting their vserver 1113266268 M * Bertl in which case you could save the init process 1113266382 M * Bertl s/save/spare/ 1113266497 M * kevinp by choosing --initstyle plain on the vserver build? 1113266534 M * Bertl which one do you have now? 1113266555 M * kevinp that's what I built my latest vserver guest with 1113266566 M * kevinp and gives no output 1113266573 M * Bertl yup, change it to sysv 1113266592 M * kevinp and that will get rid of the extra init? 1113266606 M * Bertl it will just 'try' to run the init scripts 1113266630 M * kevinp The help on vserver build does not help a lot on this: 1113266633 M * kevinp --initstyle