From owner-freebsd-bugs Fri Oct 18 01:00:04 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA04555 for bugs-outgoing; Fri, 18 Oct 1996 01:00:04 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA04537; Fri, 18 Oct 1996 01:00:02 -0700 (PDT) Date: Fri, 18 Oct 1996 01:00:02 -0700 (PDT) Message-Id: <199610180800.BAA04537@freefall.freebsd.org> To: freebsd-bugs Cc: From: J Wunsch Subject: Re: bin/1832: at(1) fails Reply-To: J Wunsch Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR bin/1832; it has been noted by GNATS. From: J Wunsch To: candy@fct.kgc.co.jp Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: bin/1832: at(1) fails Date: Fri, 18 Oct 1996 09:40:02 +0200 (MET DST) As Toshihiro Kanda wrote: > At(1) cannot open `at.deny'. Make install in /usr/src/usr.bin/at > won't fix it. This is not a bug, it's basically security restriction. If you want to losen this restriction locally, so do it. The procedure about at.deny and at.allow is explained in detail in the man page at(1). > bash$ at > at.deny: No such file or directory > You do not have permission to use at. So ask your system administrator about how you will get permission. :) It's his job. On my systems, i usually pick the `at.allow' route, i.e. i explicitly allow the use of `at' for trusted people. So you can see, these files are constituing a security policy, thus it's nothing we could provide in the default distribution. > I suggest /etc/mtree/BSD.var.dist should have more informations > of /var/at/*. BSD.var.dist does only have information about directories, not files therein. The required directories under /var/at are being created by it already. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)