I tried with both jobID (returned from qstat) and processID (returned from top) but none of them worked: Output of qstat: Job id Name User Time Use S Queue ------------------------- ---------------- --------------- -------- - ----- 344.server job1 mahmood 62:51:59 R slow 816.server job2 mahmood 03:31:25 R slow
output of top: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 26900 mahmood 20 0 235m 115m 11m R 100 0.4 0:28.42 job2 mahmood@server:~$ kill -SIGSTOP 816 -bash: kill: (816) - No such process mahmood@server:~$ kill -SIGSTOP 26900 -bash: kill: (26900) - No such process and "canceljob" actually *canceled* the job: mahmood@server:~$ canceljob 816 job '816' cancelledmahmood@server:~$ qstat Job id Name User Time Use S Queue ------------------------- ---------------- --------------- -------- - ----- 344.server job1 mahmood 62:51:59 R slow That "canceljob" was a bad command...... :( what is the difference between canceljob and qdel then???!!!! // Naderan *Mahmood; ________________________________ From: vaibhav agrawal <[email protected]> To: Mahmood Naderan <[email protected]> Cc: maui <[email protected]> Sent: Sat, January 15, 2011 5:27:20 PM Subject: Re: [Mauiusers] SIGSTOP and SIGTSTP don't work kill is the command to send the signal.check the documentation. I did tried this kill command many times, just verify the signal that needs to be send. On Sat, Jan 15, 2011 at 6:30 PM, Mahmood Naderan <[email protected]> wrote: >how abt 'kill -SIGSTOP <job-id>' >>How about 'canceljob ID' ? >When I see "kill" and "cancel", I am worry about the result. Do you have any >experience about them? Do you know exactly what happen by running those >commands? > >// Naderan *Mahmood; > > > > > ________________________________ From: vaibhav agrawal <[email protected]> > >To: Mahmood Naderan <[email protected]> >Sent: Sat, January 15, 2011 4:22:13 PM > >Subject: Re: [Mauiusers] SIGSTOP and SIGTSTP don't work > > >how abt 'kill -SIGSTOP <job-id>' > > >On Sat, Jan 15, 2011 at 5:58 PM, Mahmood Naderan <[email protected]> wrote: > >>How about 'canceljob ID' ? >>I don't want the job to be canceled. I want to suspend it >> >> >>// Naderan *Mahmood; >> >> >> >> >> ________________________________ From: andy thomas <[email protected]> >>To: Mahmood Naderan <[email protected]> >>Cc: maui <[email protected]> >>Sent: Sat, January 15, 2011 3:03:41 PM >>Subject: Re: [Mauiusers] SIGSTOP and SIGTSTP don't work >> >> >>On Sat, 15 Jan 2011, Mahmood Naderan wrote: >> >>> Hi, >>> I tested "qsig -s SIGSTOP <ID>" and "qsig -s SIGTSTP <ID>" to suspend a job >>> but >>>none of them worked. The job is still R (running). Any idea about that? >> >>How about 'canceljob ID' ? >> >>Andy >> >> >> >>_______________________________________________ >>mauiusers mailing list >>[email protected] >>http://www.supercluster.org/mailman/listinfo/mauiusers >> >> > > >_______________________________________________ >mauiusers mailing list >[email protected] >http://www.supercluster.org/mailman/listinfo/mauiusers > >
_______________________________________________ mauiusers mailing list [email protected] http://www.supercluster.org/mailman/listinfo/mauiusers
