From owner-freebsd-questions Fri May 4 19:49: 0 2001 Delivered-To: freebsd-questions@freebsd.org Received: from mtiwmhc26.worldnet.att.net (mtiwmhc26.worldnet.att.net [204.127.131.51]) by hub.freebsd.org (Postfix) with ESMTP id 4D84A37B423 for ; Fri, 4 May 2001 19:48:58 -0700 (PDT) (envelope-from parv@worldnet.att.net) Received: from worldnet.att.net ([32.101.235.152]) by mtiwmhc26.worldnet.att.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20010505024857.ICRG1648.mtiwmhc26.worldnet.att.net@worldnet.att.net> for ; Sat, 5 May 2001 02:48:57 +0000 Received: by worldnet.att.net (Postfix, from userid 1001) id 138191966B; Sat, 5 May 2001 18:49:49 -0400 (EDT) Date: Sat, 5 May 2001 18:49:48 -0400 From: parv To: f-q Subject: ksh93: jobs & kill dysfunction Message-ID: <20010505184948.A2276@moo.holy.cow> Mail-Followup-To: f-q Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i was waiting for fetchmail to finish; i sent it STOP signal via keyboard; did something unrelated. afterwords, in ksh93, i tried "jobs", nothing appeared. so thinking that fetchmail was done -- tried fetchmail again which on exit, informed me that another fetchmail process was already running. tried jobs again, still no sign of fetchmail; finally tried ps which showed old fetchmail process with status T(stopped). "well, ok. so it's stopped; will send it a CONT signal" i thought. # kill -s SIGCONT 647 # 647 - pid of the first fetchmail proc on which ksh93 barked back that there is no SIGCONT signal. "heck with it; will use bash" i was irritated now. well, that worked, same command as above. guess, next time i will just use /bin/kill next time. just venting... talking of which... is -questions the right mailing list for such vents? - parv -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message