misc/96015: uncommenting the msgs invocation in /etc/profile can fail boot

Larry Rosenman ler at lerctr.org
Tue Apr 18 16:40:14 UTC 2006

>Number:         96015
>Category:       misc
>Synopsis:       uncommenting the msgs invocation in /etc/profile can fail boot
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Tue Apr 18 16:40:12 GMT 2006
>Originator:     Larry Rosenman
>Release:        FreeBSD 6.1-RC amd64
LERCTR Consulting
System: FreeBSD thebighonker.lerctr.org 6.1-RC FreeBSD 6.1-RC #46: Sat Apr 15 23:20:33 CDT 2006 root at thebighonker.lerctr.org:/usr/obj/usr/src/sys/THEBIGHONKER amd64

I wanted to use the msgs(1) facility to have messages for my users displayed
upon login.  After I got it set up, and I uncommented the msgs -f invocation
in the system /etc/profile, my boot failed part way through, because
it wanted console input.  This caused me to have to invoke my remote hands
to fix it, since the box is colo'd. 

I'd like to request that the FreeBSD team consider making the following
2 changes:

1) change the example in /etc/profile from msgs -f to msgs -q
2) change the owner of /var/msgs in /etc/mtree/BSD.var.dist from daemon
   to mailnull so that the facility can work even after a make installworld
   on an upgrade. 

uncomment the msgs -f invocation in /etc/profile, after having a message
set up via the msgs(1) facility.`

1) change the example to msgs -q
2) change ownership in /etc/mtree/BSD.var.dist of /var/msgs to mailnull


More information about the freebsd-bugs mailing list