Re[2]: [rdiff-backup-users] Errno listing

[listserv . traffic]

Yeah, I'm only wanting to high-light problems with the backup for
user intervention - such as files that are open and can't be backed
up, destination disk full conditions etc.

I can build a list just by trial and error, but having a set of common
errors up-front would be a lot easier than going back and modifying
scripts for each installation I've got as I find different common
errors. (I'm a consultant and I'm rolling this out at a number of
different clients...) 

---
Since I'm using cygwin, I'd assume this would follow the posix
standard, right? (I prefer cygwin vs. the native Win-port because I
have easy access to ways to email exception reports etc. ...and all the
other tools in cygwin like smartmontools etc.)

TIA
-Greg

> Rdiff-backup should be handling most of these situations for you,  
> right? Are you trying to document errno's that rdiff-backup reports,  
> but recovers from, so that users won't be alarmed?

> A list of most errors which rdiff-backup handles can be found in:
> http://cvs.savannah.gnu.org/viewvc/rdiff-backup/rdiff_backup/robust.py?root=rdiff-backup&view=markup

> Look in the catch_error() function. The errno's are referred to by  
> their symbolic names, eg, EPERM, ENOENT, etc.

> determining which number they refer to is trickier, since Windows and
> POSIX use different numbers, and even on POSIX, the higher numbers can
> be different. On a Mac OS X system, you look /usr/include/sys/ernno.h
> On a Linux system, you look in /usr/include/asm-generic/errno-bash.h  
> and /usr/include/asm-generic/errno.h


> best of luck,

> Andrew


> On Mar 23, 2009, at 2:01 PM, address@hidden wrote:

>> I'm wanting to handle errno's in my bash script. I also want to add
>> to the wiki, esp as it relates to Windows/cygwin.
>>
>> But other than the trial-and-error method, I can't find any
>> documentation on the "errno" listings.
>>
>> What other common errors should I document as "regular" errors, or
>> that occur with some regularity?
>>
>> ---
>> Since most of my install base is Windows/cygwin, I'm documenting  
>> these most
>> intensely.
>>
>> ---
>>
>> Here's what I currently have...
>> [Errno 13]
>> Often seen with open PST files.
>> [However, the file name doesn't appear on the same line as "errno" so
>> I have to get the prior line that shows the actual file name we are
>> having a problem with...]
>>
>> [Errno 16]
>> Open files. (But not PST's - why these are different, I'm not
>> sure...) [The file name IS on the same line here...]
>>
>> Are there others you have seen that I should document, or handle
>> "specially?"
>>
>>
>> TIA
>> Greg
>>
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> rdiff-backup-users mailing list at address@hidden
>> http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
>> Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki



-- 
Best regards,
 listserv                            mailto:address@hidden