On Wed, Apr 12, 2006 at 09:53:37AM -0400, Jon LaBadie wrote: > On Wed, Apr 12, 2006 at 08:42:44AM -0400, stan wrote: > > On Wed, Apr 12, 2006 at 01:42:17PM +0200, Paul Bijnens wrote: > > > On 2006-04-12 12:27, stan wrote: > > > >Again, I've never done that in the past. I've just made ceratin that the > > > >amanda user exists, > > > >and done the build/make install as root. Permissions have alwasy been > > > >fine. > > > > > > > >Having sad that, I'll rebuild the whole thing today using FQDB's, and > > > >building as amanda, then > > > >installing as root. > > > > > > It is not important as who you build -- root is no problem (but > > > security minded sysadmins avoid doing things as root unless needed). > > > But the "make install" should be done as root. > > > > > > Then subsequently, you should not RUN the program as root (except > > > amrecover, which should be run as root), because when running the first > > > time, Amanda creates some files. When doing that as root - even only > > > once - those files are owned by root instead of the amanda user > > > and you run into trouble next time. > > > > Right, we are good on that. > > > > > > > > > > >BTW, speaking of rebuilding amanda, it would be nice if there were a > > > >"make > > > >no-overwrite > > > >confgis" option. > > > > > > "make install" does not install, nor overwrite any config file. > > > No need to disable that non-existing feature. > > > > > I just foudn that out, to my pleasent suprise. > > > > In any case, I rebuilt uinsg FQDN's, and I still have these problems, > > An amcheck reports: > > > > > Did your rebuild also involve rerunning "configure"?
Yes, esentialy "make distclean ; ./run_configure ; make ; su - make install > -- U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite Vietcong Terror - New York Times 9/3/1967
