for question #2 it depends how you're starting it. I have mine started by init with an entry in /etc/inittab that looks like this
Code:
SV:123456:respawn:/command/svscanboot
ps -e tells me that svscanboot is running and a bunch of supervice - <servicename> tells me that it's running and managing a bunch of services for me.
If you have made changes to your inittab you will need to send init a HUP signal to reload the changed configuration file. 'kill -HUP 1' (inetd should be a PID of 1).
If you are at all unsure of whether or not it's working properly you can try the following;
1) stop any services you started with the svc command.
2) comment out the svscanboot line in your inittab
3) kill -HUP your init
4) kill svscanboot, supervise, svscan
Now none of the daemontools should be running. Next we need to restart them i the same manner they would start at boot.
1) uncomment the svscanboot line in /etc/inittab
2) kill -HUP init
3) restart any services you want to run
If you want to run services everytime you boot you can add the command line you use to start it in your /etc/rc.local (oir whereever your rc.local is) or config your sysv runlevels to load the script upon boot.
