On Thursday 01 August 2002 07:13, Trevor Fraser wrote:
>Hi Gene, thank for your help.
>
>I used the rpm.  Two questions, what is FQDN and does rsync only
> apply to non-rpm install?

FQDN=Fully Qualified Doman Name.  This doesn't have to be registered 
anyplace but the /etc/hosts files on the machines of your subnet as 
long as /etc/host.conf sets the search order to hosts,dns.  I'm a 
bit lazy, and thats a lot easier than setting up a dns entry for 
it.  The whole point being thats its a unique name and it 
translates to THAT machines nnn.nnn.nnn.nnn address, whereas every 
machine probably has a localhost@localdomain that alias's to 
127.0.0.0, and thats whats known as a Bad Thing(TM) when you really 
meant that machine over there in the corner.  :-)

rsync isn't fussy, you can build it or use the rpm.

I use it here in exactly that scenario as I keep several of the 
directories on my firewall machine mirrored here.  rsync is  very 
efficient in that it actually moves only that which has changed.  
If you update a file, adding 20 bytes to the middle of it, rsync, 
after doing the compare, moves those 20 bytes.  It takes it about 
10 minutes to scan and update a couple of gigs worth of stuff here, 
over a 10base-T network.  Normally that machines monitor isn't 
turned on for days at a time, so other than up2date or gnorpm 
keeping the security stuff up to date, theres not a lot of 
activity.

rsync is fairly security consious, so getting the setups on both 
machines to the point of its being a crontab job will take some 
reading and a few sessions with vim, but once thats done cron will 
take care of it from there and you can convieniently forget it.

IIRC from the previous messages in this thread, you are still 
running amanda as root, and thats another no-no. IIRC the backup 
stuff will only run as the user amanda.  If it won't run as amanda, 
then you need to add the user 'amanda', and if its the rpm's, make 
her a member of the group 'disk'.  Getting all the perms setup is a 
one time job though.  Unless you've changed the owner:group of some 
of the rpm's contents, this should all work.  I guess thats one of 
the reasons I like the tarballs, you unpack them as root, chown the 
whole directory tree to amanda:disk, become amanda and build it, 
then install as root.  That takes care of *all* the perms problems.  
Amanda has her own way of becoming root when she needs root perms 
to do something.

My crontab entries to run her are in amanda's crontab, not roots.

-- 
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz  512M
99.09% setiathome rank, not too shabby for a WV hillbilly

Reply via email to