Date: Fri, 15 Aug 1997 11:56:25 -0700 (PDT) From: studded@dal.net To: FreeBSD-gnats-submit@FreeBSD.ORG Subject: bin/4308: FreeBSD uses an out of date version of vixie cron Message-ID: <199708151856.LAA26100@dalnet.webmaster.com> Resent-Message-ID: <199708151900.MAA12739@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>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: open >Class: change-request >Submitter-Id: current-users >Arrival-Date: Fri Aug 15 12:00:01 PDT 1997 >Last-Modified: >Originator: Studded >Organization: Just me :) >Release: FreeBSD 2.2.1-Release i386 >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 >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199708151856.LAA26100>