thanks Hiram - that's helpful (always important to keep the sysadmins happy). -s 15 did it for these jobs.
Janet On Mar 7, 2012, at 1:59 PM, Hiram Clawson wrote: > Good Afternoon Janet: > > Yes, your system admins will be annoyed if you run endless processes that they > are unaware of. > > Use the 'ps' command to find out the process id (PID) > of the gfServer process. Then issue a 'kill' signal to > that pid. For example: > > $ ps -ef | grep gfServer > > yourUserName 31479 31478 0 Jan12 pts/43 00:04:17 /scratch/gfServer start > hostname ... etc ... > > The second column there is the PID: 31479 > > To issue a polite kill command: > > $ kill -s 15 31479 > > If the 15 doesn't kill it, try 1 or 2 or final resort of 9 > > To see what these numbers mean for signal type: > > $ kill -l > > --Hiram > > Janet Young wrote: >> Hi there, >> I'm trying to stop three gfServers I started earlier. "gfServer stop >> hostname portname" tells me it "sent stop message to server" but doesn't >> seem to actually stop the server. I realized AFTER I started those servers >> that I should have included the "-canStop" option (another server where I >> included that does respond to the "stop" command"). >> Is there way to stop those other servers where I didn't include -canStop? >> Will my sysadmins get annoyed with me if I leave them open? >> thanks very much, >> Janet Young _______________________________________________ Genome maillist - [email protected] https://lists.soe.ucsc.edu/mailman/listinfo/genome
