Makes sense except that the /print process is different each time because it appends the directory and file name which is waiting to print. I found a way to make it fail (for testing purposes) and in turn created the check monitoring only "/print" in the of box. It turns out that this works beautifully and I now have one more thing to call my users about before they call me. Server's Alive is spectacular and has made my life exceptionally easier. Thanks again Dirk and team.
Jason Passow Mississippi Welders Supply [EMAIL PROTECTED] ph: (507) 494-5178 fax: (507) 454-8104 "If you do everything right, nobody will realize you've done anything at all." Mark Perry wrote: > You can use the *nix process monitor. > > I haven't tried it myself but it is basically the same as the NT Process > checker, click the ... Button at then end of the "of" field and it > should show all processes currently running on the chosen *nix server. > Select the relevant /print process to monitor. > > The NT process checker doesn't use wildards etc. And I believe for a > very good reason if you specifically select a process SA will monitor > that process and only that process. If wildcards were allowed then SA > would have to iterate through the services and check each and every > service with a name vaguely similar to the one you want and will give a > down result if one is wrong... Also if wildcards were allowed then > potentially a * could mean anything which would never be down as all > processes found would be running, anything missing wouldn't be noticed. > > I hope that this makes sense. > > Regards > > Mark Perry > > -----Original Message----- > From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Jason Passow > Sent: 04 August 2006 20:06 > To: Servers Alive Discussion List > Subject: [SA-list] Monitor linux server > > Let me start by saying I know next ot nothing about Linux. I am trying > to find a way to use Servers Alive to do what I must do manually after a > phone call saying stuff isn't working. > > When a user calls and tells me they are unable to print from our Linux > server application to their network printer first thing I must do is go > to a shell and run ps-ef | grep \/print. If I am correct this searches > for running processes with the command /print in it. Is there a way > to monitor such a thing using the *nix process checker? In other wards > > does the *nix process checker use a substring or a full string or accept > wildcards? > > To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list.
