From: Lukasz S. <admin-flexbackup@k.telmark.waw.pl> - 2005-03-08 23:19:51
|
Byla godzina 10:06:53 w Tuesday 08 March, gdy do autobusu wsiadl kanar i wrzasnal:"s. keeling!!! Bilecik do kontroli!!!" A on(a) na to: [...] sk> Why did it complain about bbuser and not the other users' files? The sk> permissions on his home dir are the same as everyone else's and the sk> perms on those files are correct. This one is really hard to tell since you are the only one that can see all the details. sk> Why did it go through all that then blow away the archive it was sk> creating? The index is still there, but no backup. I'd try to repeat all the moves of flexbackup by hand. Because flexbackup is "just" a script that automates things but does not do anything special itself you can try to repeat every single step fb does. sk> Why does the flexbackup command prompt me for the flexbackup user's sk> password? How am I supposed to stuff this into a cron job when that's sk> going on? Public key authentication. sk> I'm making the flexbackup user do the remote stuff via sudo. What do sk> I need to allow in /etc/sudoers for flexbackup to work? If I were you I would set all the things up the way that you backup user could log in to the server as root. There is quite an easy and safe way to do it. With openssh you can specify a command a user can invoke if authenticated with a specific public key. Browse the ssh manual pages an look for 'command=3D' and 'authorized_keys'. Czym sie cieplo s.... --=20 |/ |_, _ .- --, Ju=BF z ka=BFdej strony pe=B3zn=B1, potworne =BF= =B1dze |__ |_|. | \ |_|. ._' /_. B=EAd=EA uprawia=B3 nierz=B1d, za pieni= =B1dze |