From owner-freebsd-current Fri Jul 19 08:55:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA04557 for current-outgoing; Fri, 19 Jul 1996 08:55:55 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA04552 for ; Fri, 19 Jul 1996 08:55:52 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with SMTP id JAA12161; Fri, 19 Jul 1996 09:52:28 -0600 (MDT) Message-Id: <199607191552.JAA12161@rover.village.org> To: Joe Greco Subject: Re: various 'fetch' errors Cc: jkh@time.cdrom.com (Jordan K. Hubbard), jlemon@americantv.com, current@FreeBSD.org In-reply-to: Your message of Thu, 18 Jul 1996 22:47:27 CDT Date: Fri, 19 Jul 1996 09:52:28 -0600 From: Warner Losh Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk : While I might disagree with that description of the feature request, I : would agree that it would be better to leverage off of another tool : rather than embedding "cron/at/queue" functionality in the tool. : : Except... we don't have one. Well, I suppose you could cobble one : together with enough shell or perl programming... but maybe that : shouldn't count. There is no current tool that is easy to use that I could leverage off of to do what I want. Otherwise I would have gone out and just used that. : extensions similar to SunOS's queuedefs, it would be adequate to fill Would people be open to a queuedefs facility in at/cron? I think that would get me what I wanted and would be a useful tool for others. Warner