From swear@blarg.net  Fri Mar 15 18:12:33 2002
Return-Path: <swear@blarg.net>
Received: from lists.blarg.net (lists.blarg.net [206.124.128.17])
	by hub.freebsd.org (Postfix) with ESMTP id 6108037B400
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 15 Mar 2002 18:12:32 -0800 (PST)
Received: from thig.blarg.net (thig.blarg.net [206.124.128.18])
	by lists.blarg.net (Postfix) with ESMTP id 15E14BE56
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 15 Mar 2002 18:12:32 -0800 (PST)
Received: from localhost.localdomain ([206.124.139.115])
	by thig.blarg.net (8.9.3/8.9.3) with ESMTP id SAA14902
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 15 Mar 2002 18:12:31 -0800
Received: (from jojo@localhost)
	by localhost.localdomain (8.11.6/8.11.3) id g2G2FGr65917;
	Fri, 15 Mar 2002 18:15:16 -0800 (PST)
	(envelope-from swear@blarg.net)
Message-Id: <hpofhpcl6z.fhp@localhost.localdomain>
Date: 15 Mar 2002 18:15:16 -0800
From: "Gary W. Swearingen" <swear@blarg.net>
Reply-To: swear@blarg.net
To: FreeBSD-gnats-submit@freebsd.org
Subject: at(1) manual doesn't describe at.allow and at.deny formats.
X-GNATS-Notify:

>Number:         35942
>Category:       docs
>Synopsis:       at(1) manual doesn't describe at.allow and at.deny formats.
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    keramida
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Mar 15 18:20:01 PST 2002
>Closed-Date:    Sat May 03 14:56:15 PDT 2003
>Last-Modified:  Sat May 03 14:56:15 PDT 2003
>Originator:     Gary W. Swearingen
>Release:        FreeBSD 4.5-STABLE i386
>Organization:
none
>Environment:
n/a
================
>Description:

The at(1) manual doesn't describe the format of the at.allow and at.deny
files (in "/var/at/").

================
>How-To-Repeat:
n/a
================
>Fix:

Determine the allowed formats and add descriptions to the manual.

>Release-Note:
>Audit-Trail:

From: Giorgos Keramidas <keramida@freebsd.org>
To: "Gary W. Swearingen" <swear@blarg.net>
Cc: bug-followup@freebsd.org
Subject: Re: docs/35942: at(1) manual doesn't describe at.allow and at.deny formats.
Date: Sat, 16 Mar 2002 18:41:05 +0200

 On 2002-03-15 18:15, Gary W. Swearingen wrote:
 >
 > The at(1) manual doesn't describe the format of the at.allow and at.deny
 > files (in "/var/at/").
 >
 > >Fix:
 >
 > Determine the allowed formats and add descriptions to the manual.
 
 Well, it sort of does.  Quoting the manpage.
 
      If the file /var/at/at.allow exists, only usernames
      mentioned in it are allowed to use at.
 
 This needs to be made more descriptive though.
 What do you think of the following?
 
 Index: at.man
 ===================================================================
 RCS file: /home/ncvs/src/usr.bin/at/at.man,v
 retrieving revision 1.27
 diff -4 -u -r1.27 at.man
 --- at.man	15 Mar 2002 15:26:57 -0000	1.27
 +++ at.man	16 Mar 2002 16:38:17 -0000
 @@ -173,16 +173,22 @@
  If the file
  .Pa _PERM_PATH/at.allow
  exists, only usernames mentioned in it are allowed to use
  .Nm .
 +Add the names of the users that should be allowed to run
 +.Nm
 +to this file, one per line.
  .Pp
  If
  .Pa _PERM_PATH/at.allow
  does not exist,
  .Pa _PERM_PATH/at.deny
  is checked, every username not mentioned in it is then allowed
  to use
  .Nm Ns .
 +Add the names of the users that should not be allowed to run
 +.Nm
 +to this file, one per line.
  .Pp
  If neither exists, only the superuser is allowed use of
  .Nm Ns .
  This is the default configuration.
 
 Giorgos Keramidas                       FreeBSD Documentation Project
 keramida@{freebsd.org,ceid.upatras.gr}  http://www.FreeBSD.org/docproj/

From: swear@blarg.net (Gary W. Swearingen)
To: Giorgos Keramidas <keramida@freebsd.org>
Cc: bug-followup@freebsd.org
Subject: Re: docs/35942: at(1) manual doesn't describe at.allow and at.deny formats.
Date: 17 Mar 2002 12:54:09 -0800

 Giorgos Keramidas <keramida@freebsd.org> writes:
 
 Much of what you added is already explained in the manual in a less
 ambiguous manner.  I fear that your addition (especially for "deny")
 will confuse some readers.  Please excuse my bluntness.
 
 Better to limit your addition to the format of the file, which in your
 patch is "one per line".  And since users often make guesses about what
 might be allowed, namely leading or trailing whitespace and comments, it
 should "head off" failed experiments by being explicit on those topics.
 
 I haven't looked at the code and so won't propose wording, but for the
 crontab(1)'s manual, my patch contained
 
     In these two files, a user is considered to be listed only if the
     user name has no blank or other characters before it on its line and
     a newline character immediately after the name, even at the end of
     the file.  Other lines are ignored and may be used for comments.
 
 This was discussed back in October along with discussion of changing the
 program's end-of-file behavior, but I don't see any changes in the 4.5
 crontab manual and I do see that users see it dated "1993"; both bad
 "PR", in one sense or another. :)
State-Changed-From-To: open->patched 
State-Changed-By: keramida 
State-Changed-When: Tue Mar 25 18:38:28 PST 2003 
State-Changed-Why:  
Finally get around to testing and committing the excellent 
suggestion of Gary. 


Responsible-Changed-From-To: freebsd-doc->keramida 
Responsible-Changed-By: keramida 
Responsible-Changed-When: Tue Mar 25 18:38:28 PST 2003 
Responsible-Changed-Why:  
I'll do teh MFC. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=35942 
State-Changed-From-To: patched->closed 
State-Changed-By: keramida 
State-Changed-When: Sat May 3 14:55:56 PDT 2003 
State-Changed-Why:  
Merged to RELENG_4. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=35942 
>Unformatted:
