On Tue, 2002-06-11 at 10:46, Christoph Scheeder wrote: > Hi, > > > amanda@sevenof9 amanda]$ tar --version > > tar (GNU tar) 1.13.25 > > > Good, this is a version that should be ok.
Good, I'm glad that isn't the problem. > > [amanda@sevenof9 amanda]$ rpm -qa | grep samba > > samba-common-2.2.3a-6 > > samba-client-2.2.3a-6 > > > Sorry to correct you, latest recommended version of samba on samba-homepage > is 2.2.4, but i'll bet it won't do anything good to upgrade to that version, > but give you lots of trouble if you have samba as pdc and nt boxes as clients, > but thats little off-topic... Ah you're right, there is a later version but as you say, it does not address any problems that would be affecting this issue. > > I don't think it will help you. > > But something other comes to my mind: > what version of windows do the files reside on? > WIN-NT/2000/XP ? > if yes, has the backup user the permision to see and read these files? This is a W2K box being backed up, yes.. and I have made sure permissions are set properly, since the level 0 has permission to read and write those files (the user and password are listed in the /etc/amandapass file) I assumed that the level 1 would also have permission to read/write those files. The amrecover is running as root, which wouldn't have any special permission on the W2K box.. but it wouldn't be logging in as root to the W2K box during a local recover, would it? > > if that's not the problem i've reached the end of my knowledge. ahh. well I certainly appreciate your trying. Any other thoughts from the list? It seems like this should be easy to reproduce, has anyone had this happen using Samba on their systems? \marc
