From owner-freebsd-bugs Mon Feb 17 21:36:08 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA21548 for bugs-outgoing; Mon, 17 Feb 1997 21:36:08 -0800 (PST) Received: from labs.usn.blaze.net.au (labs.usn.blaze.net.au [203.17.53.30]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA21462 for ; Mon, 17 Feb 1997 21:35:59 -0800 (PST) Received: (from davidn@localhost) by labs.usn.blaze.net.au (8.8.5/8.8.5) id QAA26564; Tue, 18 Feb 1997 16:35:27 +1100 (EST) Message-ID: <19970218163527.12178@usn.blaze.net.au> Date: Tue, 18 Feb 1997 16:35:27 +1100 From: David Nugent To: J Wunsch Cc: freebsd-bugs@freefall.freebsd.org Subject: Re: bin/2747: at cannot be run in an atjob References: <199702172200.OAA18446@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61 In-Reply-To: <199702172200.OAA18446@freefall.freebsd.org>; from J Wunsch on Feb 02, 1997 at 02:00:01PM Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Feb 02, 1997 at 02:00:01PM, J Wunsch wrote: > I think atrun(8) should rather call setlogin(), the at(1) falling over > the missing login name is only one examle of a failing program -- > there might be more of them. atrun(8) should actually call setusercontext() (which can optionally do the setlogin()) since there is currently no resource limit guard as well. It will currently run at daemon limits and priority. This one slipped by, but I've added it to my todo list. Regards, David Nugent - Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/