Subject: RELEASE bailed creating alias DB
To: None <port-pmax@netbsd.org>
From: NetBSD Mailing list <netbsd@mrynet.com>
List: port-pmax
Date: 02/12/2000 00:30:50
This is a new failure on an previously successful RELEASE setup
(as recently as 1.4Q):
(cd ../usr.bin/mail; make distribution)
cd /abyss/ftp/pub/operatingsystems/NetBSD/pmax-src/src/usr.bin/mail/misc; install -c -o root -g wheel -m 644 mail.rc /gorge/pmax/live/etc (cd ../gnu/usr.sbin/sendmail/cf/cf; make distribution)
install -c -o root -g wheel -m 444 netbsd-proto.cf /gorge/pmax/live/etc/sendmail.cf
/gorge/pmax/live/usr/libexec/sendmail/sendmail -C /gorge/pmax/live/etc/sendmail.cf -O AliasFile=/gorge/pmax/live/etc/aliases -bi
WARNING: Group writable directory /gorge
hash map "Alias0": unsafe map file /gorge/pmax/live/etc/aliases.db: Group writable directory
WARNING: cannot open alias database /gorge/pmax/live/etc/aliases
Cannot create database for alias file /gorge/pmax/live/etc/aliases
*** Error code 71
Stop.
mod60# ls -ld /gorge /gorge/pmax /gorge/pmax/live
drwxrwx--x 12 root wheel 512 Jan 28 03:09 /gorge
drwxr-xr-x 4 root wheel 512 Feb 12 00:11 /gorge/pmax
drwxr-xr-x 14 root wheel 512 Feb 12 00:08 /gorge/pmax/live
Changing /gorge to rwxr-x--x resolves this:
(cd ../gnu/usr.sbin/sendmail/cf/cf; make distribution)
install -c -o root -g wheel -m 444 netbsd-proto.cf /gorge/pmax/live/etc/sendmail.cf
/gorge/pmax/live/usr/libexec/sendmail/sendmail -C /gorge/pmax/live/etc/sendmail.cf -O AliasFile=/gorge/pmax/live/etc/aliases -bi
/gorge/pmax/live/etc/aliases: 19 aliases, longest 10 bytes, 209 bytes total
/bin/rm -rf /gorge/pmax/release
install -d -o root -g wheel -m 755 /gorge/pmax/release
(RELEASE build continues)
This must be a recent change, since I've been building snapshots under the
same structure previously.
Is this really a proper check when building RELEASE? Basically this limitation
is demanding that the entire tree up to the RELEASE root be non-group and
non-world writable.
Since this did work before, as /gorge hasn't changed permissions, I'll ask
if this isn't something that should be considered changed back. beyond that
I will have to work something else out as this particular partition does
indeed need group write access at the root level.
Cheers,
-skots
--
Scott G. Akmentins-Taylor InterNet: staylor@mrynet.com
MRY Systems staylor@mrynet.lv
(Skots Gregorijs Akmentins-Teilors -- just call me "Skots")
----- Labak miris neka sarkans -----