From owner-freebsd-bugs Fri Aug 22 00:09:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA22027 for bugs-outgoing; Fri, 22 Aug 1997 00:09:54 -0700 (PDT) Received: from merchant.tns.net (tcilx.terracom-usa.com [204.216.142.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA22022 for ; Fri, 22 Aug 1997 00:09:51 -0700 (PDT) Received: (from tiller@localhost) by merchant.tns.net (8.8.6/8.8.6) id AAA27262; Fri, 22 Aug 1997 00:04:47 -0700 (PDT) Message-Id: <199708220704.AAA27262@merchant.tns.net> From: "Studded" To: "David Nugent" Cc: "freebsd-bugs@freebsd.org" Date: Fri, 22 Aug 97 00:09:10 -0700 Reply-To: "Studded" Priority: Normal X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: bin/4308 (cron leaves artifacts when starting a process) Sender: owner-freebsd-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 21 Aug 1997 14:01:21 +1000, David Nugent wrote: >However, since you're building piecemeal on an older system, it is probably >easier just to remove the -DLOGIN_CAP from the CFLAGS definition in cron's >Makefiles. Ok, this got it built, thanks for the tip. :) Unfortunately, the new cron didn't solve the problem. Using sources from 2.2.2-Stable (8/18) I got the exact same effect when it was necessary to start adjkerntz. Here is the cron job: */2 * * * * root /bin/sh /root/test.sh Here is the sh script I was using to test: #!/bin/sh /bin/ps -ax | /usr/bin/grep [a]djkerntz ec=$? if [ $ec != 0 ]; then /sbin/adjkerntz -i & fi exit And here is what got left over when adjkerntz was not running, and the script had to start it: 15658 ?? Ss 0:00.01 /usr/sbin/cron 15685 ?? S 0:00.00 /USR/SBIN/CRON (cron) 15686 ?? Z 0:00.00 (sh) 15692 ?? Ss 0:00.00 /sbin/adjkerntz -i As before, a kill for 15685 eliminated the zombie too. I tried this with some other processes (named, snmpd, ircd) with and without command line arguments, and with and without an & at the end of the line to bg the process, and I didn't get any artifacts like the ones above. Also, I tried it with a stock 2.2.1 system and started named instead of adjkerntz, and didn't get the artifacts with that either, although I'm seeing them on a 2.2.2-R system when a process is being started from a perl script too. It'll still be a few days before I can set up a 2.2.2-Stable system, but if there is anything else I can do to test it, let me know. Doug Do thou amend they face, and I'll amend my life. -Shakespeare, "Henry V"