From studded@dalnet.webmaster.com  Fri Aug 15 11:56:30 1997
Received: from dalnet.webmaster.com (dalnet.webmaster.com [206.86.127.216])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA12564
          for <FreeBSD-gnats-submit@freebsd.org>; Fri, 15 Aug 1997 11:56:28 -0700 (PDT)
Received: (from studded@localhost) by dalnet.webmaster.com (8.8.5/8.7.3) id LAA26100; Fri, 15 Aug 1997 11:56:25 -0700 (PDT)
Message-Id: <199708151856.LAA26100@dalnet.webmaster.com>
Date: Fri, 15 Aug 1997 11:56:25 -0700 (PDT)
From: studded@dal.net
Reply-To: studded@dal.net
To: FreeBSD-gnats-submit@freebsd.org
Subject: FreeBSD uses an out of date version of vixie cron
X-Send-Pr-Version: 3.2

>Number:         4308
>Category:       bin
>Synopsis:       FreeBSD uses an out of date version of vixie cron
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Fri Aug 15 12:00:01 PDT 1997
>Closed-Date:    Thu Mar 12 03:18:16 PST 1998
>Last-Modified:  Thu Mar 12 03:19:30 PST 1998
>Originator:     Studded
>Release:        FreeBSD 2.2.1-Release i386
>Organization:
Just me :)
>Environment:

	Not relevant.

>Description:

	I've sent a couple letters to -questions about this, but to
summarize, when a process is started from an sh or perl script that is run
by cron, it leaves artifacts similar to this:

6591  ??  I      0:00.01 CRON (cron)
6592  ??  Z      0:00.00  (sh)


>How-To-Repeat:

	Start a process from a script run by cron.

>Fix:
	
	I finally wrote to Paul Vixie about this who was kind enough to
respond with a simple answer, "old code."  He pointed me to
ftp.vix.com/pub/vixie where the latest version is 3.0.  Our version has
changes that date after the release of 3.0 in 1994, so I'm not sure
exactly what needs to be changed, but I would really appreciate it if
someone smarter than me could poke around. :)

	If someone can come up with patches against 2.2.1-R I'll be happy
to test them to see if it resolves the problem I describe.

Thanks,

Doug

PS, if my address doesn't come out right, I can be reached at
Studded@dal.net
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: andreas 
State-Changed-When: Sun Aug 17 17:20:08 MEST 1997 
State-Changed-Why:  

could you please update your system to 2.2-STABLE and re-try ? 

From: Studded <Studded@dal.net>
To: freebsd-gnats-submit@freebsd.org
Cc:  Subject: Re: bin/4308: FreeBSD uses an out of date version of vixie cron
Date: Thu, 12 Mar 1998 03:05:22 -0800

 The behavior described in the PR still occurs, however all indications
 are that the zombies are harmless, and related to the failure of the
 process started by the script to fork and/or background itself properly.
 Additionally, the version of cron in use currently is the most recent
 version, plus various fixes. 
 
 	In other words, go ahead and close this. :)
 
 Doug
 -- 
 ***         Chief Operations Officer, DALnet IRC network       ***
 *** Proud operator, designer and maintainer of the world's largest
 *** Internet Relay Chat server.  5,328 clients and still growing.
 *** Try spider.dal.net on ports 6662-4    (Powered by FreeBSD)
State-Changed-From-To: feedback->closed 
State-Changed-By: eivind 
State-Changed-When: Thu Mar 12 03:18:16 PST 1998 
State-Changed-Why:  
Closed at the request of the originator. 
>Unformatted:
