Warning messages from fbackup

[John Walker_1]

Canyone advise whether or not you can filter out the warning messages that fbackup generates when a file is not backed up, ie:fbackup(3005): WARNING: file number 310 was NOT backed up??

[Deepak Extross]

Hi,
You can always redirect stderr to /dev/null if you want to suppress errors.
Anyway, this warning indicates that the file was moved *after* fbackup started and *before* it could reach the specified file. If this was a temporary file of some kind, you can probably ignore the warning.

[Deepak Extross]

And if you want to blindly filter out these warnings, there's always
grep -v "fbackup\(3005\)\: WARNING"

HTH,
Deepak.

[John Walker_1]

I know I can pull them out afterwards, I just wondered if they can be prevented from being put int the log. I dont want to suppress all warnings as some can be useful but this one isnt! - thanks anyway.

[Paula J Frazer-Campbell]

John

Are you backing up tmp dirs ?

/tmp
/var/tmp

Is so why?

Paula

[Mark Vollmers]

John-

You can take the log after backup runs and pull out the items and save it somewhere, using that new file as the copy you look at. Do you normally have a lot of these? I get one or two with my backups. If you have enough of them that it makes looking over the results difficult, I'd have to agree with the others and say that maybe the best course would be to leave the log intact (there might be a file not backed up that you actually care about someday) and try to avoid backing up those directories where your files appear (temp locations). Just a thought.

Mark