Bug 102225 – dnrd file permission error

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Martin Hierling 2005-08-12 04:56:25 UTC]

After installing dnrd 2.19.1 i got this error in my syslog:

Aug 12 13:02:03 pille groupadd[24812]: new group: name=dnrd, gid=409
Aug 12 13:02:04 pille useradd[24836]: new user: name=dnrd, uid=102, gid=409,
home=/etc/dnrd, shell=/bin/false
Aug 12 13:08:22 pille /dnrd[26068]: The /etc/dnrd directory must be owned by root
Aug 12 13:09:23 pille rc-scripts: WARNING:  "dnrd" has already been started.

Line 1 und 2 are from the install ebuid, they are ok. Line 3 tells me that
/etc/dnrd has wrong permissions and startup script of dnrd tells me service is
up, but it isnt. chown root /etc/dnrd fixed the problem. 

Reproducible: Always
Steps to Reproduce:
1.
2.
3.




ortage 2.0.51.22-r2 (!/usr/portage/profiles/default-linux/x86/2005.0,
gcc-3.3.5-20050130, glibc-2.3.5-r0, 2.6.11.10-xen i686)
=================================================================
System uname: 2.6.11.10-xen i686 Intel(R) Xeon(TM) CPU 2.00GHz
Gentoo Base System version 1.6.13
dev-lang/python:     2.3.5
sys-apps/sandbox:    1.2.11
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.5
sys-devel/binutils:  2.15.92.0.2-r10
sys-devel/libtool:   1.5.18-r1
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O2 -march=i686 -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config
/usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=i686 -fomit-frame-pointer"
DISTDIR="/mnt/net/distfiles"
FEATURES="autoconfig buildpkg distlocks sandbox sfperms strict"
GENTOO_MIRRORS="ftp://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/
ftp://mirrors.sec.informatik.tu-darmstadt.de/gentoo/
http://linux.rz.ruhr-uni-bochum.de/download/gentoo-mirror/
ftp://ftp6.uni-muenster.de/pub/linux/distributions/gentoo"
PKGDIR="/mnt/net/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/mnt/net/portage"
PORTDIR_OVERLAY="/usr/local/portage/gentoo-de"
SYNC="rsync://rsync16.de.gentoo.org/gentoo-portage"
USE="x86 apm arts avi berkdb bitmap-fonts crypt cups curl emboss encode
foomaticdb fortran gd-external gdbm gif gpm imlib ipv6 jpeg libg++ libwww mad
maildir mbox mikmod motif mp3 mpeg mysql ncurses nls oggvorbis opengl oss pam
pdflib perl png python quicktime readline sdl ssl tcpd truetype-fonts
type1-fonts xml2 xmms xv zlib userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS

[Comment 1 Chris White (RETIRED) 2005-08-12 20:53:09 UTC]

How are you starting dnrd?  Mine is done by the init.d script the author 
provided for me, which takes the user down to a restricted level (prevents 
security breaches). 

[Comment 2 Martin Hierling 2005-08-15 03:26:15 UTC]

as it is supposed to do: with tihe init script as unprev. user "dnrd":
dnrd     26353     1  0 Aug12 ?        00:00:00 /usr/sbin/dnrd --uid dnrd
--address 127.0.0.1 --log --server 193.16.xxx.yy --server 193.16.xxx.yz

see log, try for yourself:

pille ~ # /etc/init.d/dnrd stop
 * Caching service dependencies ...                                            
                                                            [ ok ]
 * Stopping dnrd ...                                                           
                                                            [ ok ]
pille ~ # chown dnrd /etc/dnrd/
pille ~ # /etc/init.d/dnrd start
 * Starting dnrd ...                                                           
                                                            [ ok ]
pille ~ # date
Mon Aug 15 12:23:41 MEST 2005
pille ~ # grep dnrd /var/log/messages
Aug 15 12:23:27 pille /dnrd[32666]: The /etc/dnrd directory must be owned by root
pille ~ # ps -ef| grep dnrd
root     32708 32317  0 12:23 pts/1    00:00:00 grep dnrd
pille ~ # chown root /etc/dnrd/
pille ~ # /etc/init.d/dnrd start
 * WARNING:  "dnrd" has already been started.
pille ~ # /etc/init.d/dnrd zap
 * Manually resetting dnrd to stopped state.
pille ~ # /etc/init.d/dnrd start
 * Starting dnrd ...                                                           
                                                            [ ok ]
pille ~ # ps -ef| grep dnrd
dnrd       354     1  0 12:24 ?        00:00:00 /usr/sbin/dnrd --uid dnrd
--address 127.0.0.1 --log --server 193.16.xxx.yy --server 193.16.xxx.yz
root       360 32317  0 12:24 pts/1    00:00:00 grep dnrd

[Comment 3 Chris White (RETIRED) 2005-08-15 07:43:33 UTC]

Can you do me a favor and attach the current /usr/portage/eutils.eclass you 
have (without an emerge --sync). 

[Comment 4 Martin Hierling 2005-08-15 23:02:03 UTC]

Created attachment 66053 [details]
Eutils.eclass

Sync History
     rsync'ed at >>> Wed Aug  3 13:01:40 2005
     rsync'ed at >>> Wed Aug  3 13:47:45 2005
     rsync'ed at >>> Thu Aug  4 19:31:56 2005
     rsync'ed at >>> Mon Aug  8 15:40:01 2005
     rsync'ed at >>> Thu Aug 11 09:18:47 2005
     rsync'ed at >>> Sat Aug 13 15:11:26 2005

[Comment 5 Martin Hierling 2005-08-15 23:03:56 UTC]

Created attachment 66054 [details]
right version, 1st was wrong

Rsync History
     rsync'ed at >>> Wed Aug  3 13:01:40 2005
     rsync'ed at >>> Wed Aug  3 13:47:45 2005
     rsync'ed at >>> Thu Aug  4 19:31:56 2005
     rsync'ed at >>> Mon Aug  8 15:40:01 2005
     rsync'ed at >>> Thu Aug 11 09:18:47 2005
     rsync'ed at >>> Sat Aug 13 15:11:26 2005

[Comment 6 Chris White (RETIRED) 2005-08-17 09:53:44 UTC]

Hmm.. seems I had a different run of events since the last time I tested dnrd.  
The whole permissions thing wasn't an issue then.  Anyways, this is now fixed 
in cvs.