From: Freddie C. <fc...@sd...> - 2003-01-23 19:21:48
|
On January 23, 2003 07:54 am, Randall Perry wrote: > > On 23 Jan 2003 at 12:46, Jamie Cameron wrote: > >> Randall Perry <rg...@sy...> wrote .. > >>> Noticed there's no server monitor for Proftpd. Any plans for one? > >> There isn't one because proftpd (and wu-ftpd) are usually run from > >> inetd, and so don't have a server process to check. Instead you coul= d > >> use the 'Remote TCP Service' monitor to check if something is listen= ing > >> on the FTP port 21. > > Just out of curiosity, why would anyone run ProFTPd via Inetd?? It i= s > > more than capable (and even recommended) to run it standalone. > > That being said, all that's really needed is the "Check Process" > > monitor and tell it to look for proftpd. Works like a charm (using i= t > > on 12 different servers). > What do put in 'Command to check for' field? A command that returns a > boolean value? Using the "Check Process" monitor, fill in the "Command to Check For" fie= ld=20 with "proftpd". This is the value that shows up when you do a "ps" on th= e=20 system. I use the "Check Process" monitor to check if all my various daemons are=20 running. Makes it a little simpler as I only have to worry about a singl= e=20 type of process monitor to configure. They all work the same, and don't = have=20 to worry about pid files or whatnot. --=20 Freddie Cash=09=09=09District Help Desk / Network Admin fc...@sd...=09=09helpdesk.sd73.bc.ca =09=09=09=09(250) 374-0679 ext. 217 |