Hi Sue - I guess I know the cause of my problem - if a system is using shadow passwords (as does Linux) one has to - use -DSHADOWPW (as you suggested) when building rootd - run rootd as root via inetd, otherwise the daemon wouldn't have access to shadow password file, which can be accessed only by root So now it looks that rootd started by a regular (non-root) Linux user just wouldn't be able to do authentication. If this is the case, it might be a good idea to reflect it in the documentation. best, Pasha Susan Kasahara wrote: > > Hi Pasha, > I haven't investigated the details of your problem, but one thing that comes to mind when > reading your message is a problem that I first encountered with authentication errors > when using rootd on a system that supports shadow passwords. The solution was that > to run rootd on systems that support shadow passwords (which it looks like is your case), > you have to recreate the rootd binary with the -DSHADOWPW compiler flag set. The > steps that I followed were: > a)Download the ROOT source code from http://root.cern.ch. Unpack to > $ROOTSYS/src (you must have already installed the regular ROOT distribution > before downloading the source code). > b)cd $ROOTSYS/src > c)ln -s Makefile.linuxegcs makefile (or pick the Makefile appropriate for > your platform) > d)edit the makefile and add -DSHADOWPW to the CXXFLAGS and CFLAGS lists > e)make distclean > f)make > This will remake the entire root distribution (libraries and binaries) > (which is overkill of course, I'm sure you can figure out a way to just recreate the rootd binary if you don't > want it all.) > In any case, that fixed my authentication error problem. > Good luck, > Sue Kasahara
This archive was generated by hypermail 2b29 : Tue Jan 02 2001 - 11:50:17 MET