From andrew@sally.ugh.net.au  Tue Mar 18 08:25:34 1997
Received: from who.cdrom.com (who.cdrom.com [204.216.27.3])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA02521
          for <FreeBSD-gnats-submit@FreeBSD.ORG>; Tue, 18 Mar 1997 08:25:33 -0800 (PST)
Received: from sally.ugh.net.au (sally.hobart.tasED.edu.au [147.41.41.101])
          by who.cdrom.com (8.8.5/8.6.11) with ESMTP id HAA00547
          for <FreeBSD-gnats-submit@freebsd.org>; Tue, 18 Mar 1997 07:48:48 -0800 (PST)
Received: (from andrew@localhost)
	by sally.ugh.net.au (8.8.5/8.8.5) id XAA00288;
	Tue, 18 Mar 1997 23:30:03 +1100 (EST)
Message-Id: <199703181230.XAA00288@sally.ugh.net.au>
Date: Tue, 18 Mar 1997 23:30:03 +1100 (EST)
From: Andrew <andrew@sally.ugh.net.au>
Reply-To: andrew@ugh.net.au
To: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: msgs - permission denied.
X-Send-Pr-Version: 3.2

>Number:         3023
>Category:       conf
>Synopsis:       By default users have no write permission to /var/msgs
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Tue Mar 18 08:30:03 PST 1997
>Closed-Date:    Mon Jul 27 18:15:16 PDT 1998
>Last-Modified:  Mon Jul 27 18:16:02 PDT 1998
>Originator:     Andrew
>Release:        FreeBSD 2.2-RELEASE i386
>Organization:
>Environment:

Fresh 2.2-R install.

>Description:

When running msgs it checks the file /var/msgs/bounds to quickly see if there are any new messages. If the file doesn't exist then msgs creates it. Unfortunately only when run by root does msgs have permission to create this file - everyone else gets an error until root runs msgs.

>How-To-Repeat:

Type msgs on a 2.2-R system.

>Fix:
	
Many ways I guess:

1) Change permissions on /var/msgs to allow anyone to write to it (not a good idea)

2) Make msgs set-uid to someone with permissions to write to /var/msgs (probably not to good either)

3) Have the installer create a bounds file (not sure if you can do this if there aren't any messages - I guess you could say last msg was -1 or 0 depending on how they are numbered).

There are probably oher ways (from my list I prefer 3). I don't know what the 'proper' method is.
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: nectar 
State-Changed-When: Mon Jul 27 18:15:16 PDT 1998 
State-Changed-Why:  
fixed in -CURRENT, rev 1.147 of etc/rc 
>Unformatted:
