Date: Fri, 18 Oct 1996 01:00:02 -0700 (PDT) From: J Wunsch <j@uriah.heep.sax.de> To: freebsd-bugs Subject: Re: bin/1832: at(1) fails Message-ID: <199610180800.BAA04537@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/1832; it has been noted by GNATS. From: J Wunsch <j@uriah.heep.sax.de> 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. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199610180800.BAA04537>