The behavior is inconsistent. For Apache, when run from
Webmin, runs fine and Status Monitor in Webmin correct,
but processes are hidden from root 'ps' in console
window. As a result, you can't stop Apache server from
the console if you started it from Webmin. And if you
started it from a console, you can't stop it Webmin,
because Webmin status monitor doesn't see it runnning.
Same behavior for Qmail, UNLESS you overide the
start/stop/hup commands. I changed each to use the
qmailctl command, and now the processes can be
started from Webmin, but Status Monitor can't tell they
are running, so Qmail module won't give option to allow
stop. In this case, the processes are visible in
console 'ps', but not under Webmin Running Processes.
Why the segregation of processes in one case but not
the other? Why segregation at all?
Thanks,
Wayne
System: vserver jail running FreeBSD 4.8, Webmin 1.170
Logged In: YES
user_id=129364
I think this may have something to do with the fact Webmin
is running under a vserver jail - perhaps it is effectively
in a different vserver from the one you are in when you
login via SSH?
Logged In: YES
user_id=237546
I don't think so, my understading is you can't interact with
anything outside your jail. The jail is the whole world as far as
you're concerned. Also, the PIDs themselves are created in
correct sequence, using the next available PID for that jail,
just not visible when started from Webmin.
But what clinches it is if you tell it to start Qmail
using 'qmailctl start' rather than keep the default setting in
Webmin, the PIDs are visible even though started from
Webmin.
So the clue lies in the process invocation code, and the
difference betweem running Qmail with default command, vs
running it with a specified command.
Logged In: YES
user_id=129364
It sort of looks to me like Webmin is running outside the
jail, and your command-line login is within it.
By the way, the command used to start Qmail by default is
just /var/qmail/rc ..