Hi,
07.11.2007 23:10,, Eric Böse-Wolf wrote::
> Hello Arno,
>
>> There will be some reason why your tapealert command output isn't
>> matched by grep. You'll ony see what happens behind the scenes if you
>> try the tapealert command Bacula runs and look at the output, not
>> piped through grep
Hello Arno,
> There will be some reason why your tapealert command output isn't
> matched by grep. You'll ony see what happens behind the scenes if you
> try the tapealert command Bacula runs and look at the output, not
> piped through grep.
This is a misunderstanding or maybe I didn't tell yo
Hi,
07.11.2007 13:48,, Eric Böse-Wolf wrote::
> Hello Arno,
> Arno Lehmann <[EMAIL PROTECTED]> writes:
>
>>> Reading the man page of grep I noticed that it exits with exit code 1 if
>>> it does not find the pattern searched for, so I should have had the same
>>> error message with my autochanger,
Hello Arno,
Arno Lehmann <[EMAIL PROTECTED]> writes:
>> Reading the man page of grep I noticed that it exits with exit code 1 if
>> it does not find the pattern searched for, so I should have had the same
>> error message with my autochanger, shouldn't I?
> I'd start with trying the actual tapeal
Hi,
07.11.2007 09:41,, Eric Böse-Wolf wrote::
> Today I switched from using an autochanger to using a single drive and
> updated the alert command to sh -c "tapeinfo -f /dev/sg1 | grep
> 'TapeAlert'" and now bacula complains about a bad alert command, as it
> exits with exit code 1.
>
> Reading t
Today I switched from using an autochanger to using a single drive and
updated the alert command to sh -c "tapeinfo -f /dev/sg1 | grep
'TapeAlert'" and now bacula complains about a bad alert command, as it
exits with exit code 1.
Reading the man page of grep I noticed that it exits with exit code
