On 15 Feb 2002 at 6:02am, [EMAIL PROTECTED] wrote > It did produce the following error however. I am not a Windows person > so I don't know, but I presume from the file name that this is something > to do with the Windows swap space and it is normal. If so, should I > expect to see it every day, or is there a way to prevent it? > > FAILED AND STRANGE DUMP DETAILS: > > /-- gorn.ameri //zena/C lev 0 STRANGE > sendbackup: start [gorn.americom.com://zena/C level 0] > sendbackup: info BACKUP=/usr/bin/smbclient > sendbackup: info RECOVER_CMD=/usr/bin/smbclient -f... - > sendbackup: info end > | Added interface ip=192.168.2.1 bcast=192.168.2.255 nmask=255.255.255.0 > ? ERRDOS - ERRbadshare opening remote file \WINDOWS\WIN386.SWP (\WINDOWS\) > | tar: dumped 12935 tar files > | Total bytes written: 639080448 > sendbackup: size 624102 > sendbackup: end > \--------
You're exactly right -- that's the swap file, and you can't open it. You could exclude it in your dumptype, or just ignore the error. > Can anyone tell me what the C$ means and why (in my case) it worked only > when I used C without the $ sign? > C$ is the default administrative share that Windows always creates (*sigh*). This is done for every partition. I have no idea why you can't get that and can get C to work. Oh, and isn't the Warrior Princess going to be upset that you misspelled her name? ;) -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
