The process is similar to "/bin/print /tmp/queue/ABCDEFG.123" (with a bunch of other stuff including username printer name etc.), where the ABDEFG.123 is random. So I want to find out if I have a lot of jobs using the /bin/print function. So you are correct in the ps checker I entered just /print (no quotes no *). In this case, it returns how many processes are running that contain /print. I only alert if there is more than one job. It would be nice however to list each process or something. It is not that big of deal since I need to log in to kill the job but if it is some sort of large report it would sit in the queue for a bit. If I had the entire process name it would tell me what type of job is waiting and I wouldn't need to log in then.
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: > Sorry did you use a wildcard I thought you just put in "/print" as a > generic statement... Am I confused I think I am. > > I do have query though, what do you mean by 'my substring' if you > already know the string then you can inject the text using the built in > vb script of SA. You can pass %e to a script to re-format. > > -----Original Message----- > From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Jason Passow > Sent: 04 August 2006 20:41 > To: Servers Alive Discussion List > Subject: Re: [SA-list] Monitor linux server > > One more question on this topic. So since I have discovered that the > wildcard works is there anyway to return the whole string that contains > my substring in the %e variable. > > 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. > > 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. > > 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.
