Debra S Baddorf <[email protected]> writes: >>>> >> Normally you build amanda in the /home/amanda directory, sudo -i, >> then su amanda. Then when its built, ctrl-D out of amanda and make >> install as root, then your perms are all as they should be. I have a >> configure driver file to configure and build, and It won't do a thing if >> I'm root. Thats a bad dog, no biscuit if not the user amanda. > > Group people (not just Gene): > Does it still matter which acount builds and which account installs amanda?
Yes, it does matter. You never know what could get wrong when building a package, so you better do the build in a lower priviledged account, like your normal user account. There is no reason why you need higher priviledges to run a compile, so the safe way is to use the less proviledges all the time. Then you do a test, and Unix is good that usually you can do the test while still loged in the lower proviledged account. Then you install with root account: you need root proviledges to install because you need to create directories where other users can't, you may need to create new users too (like user amanda). Best regards, Olivier > I do “ksu root” (kerberos su) > and build and then install. All as root. In a /tmp/amanda-builds > directory. > Sometimes multiple times, if I’m comparing or testing something. > > It always works for me. I never switch back to my amanda user to do the > build or the install. > > My amanda user is operator:root, in case that makes a difference. > amanda versions up to (now) 3.3.8. > We use SLF, Scientific Linux Fermilab (locally modified for science; > available every where, I think) > > Deb Baddorf > Fermilab > > --
