Stephen Gran a écrit :
>This one time, at band camp, KaalH! said:
>
>
>>Stephen Gran a écrit :
>>hum, you're right about the "standard practice", but isn't "invoke-rc.d
>>--quiet foo reload > /dev/null" better ?
>>
>>I think "...freshclam > /dev/null" redirect stdout only, and
>>"...freshclam 2>
This one time, at band camp, KaalH! said:
> Stephen Gran a écrit :
> hum, you're right about the "standard practice", but isn't "invoke-rc.d
> --quiet foo reload > /dev/null" better ?
>
> I think "...freshclam > /dev/null" redirect stdout only, and
> "...freshclam 2>&1 > /dev/null" redirect stderr
Stephen Gran a écrit :
>This one time, at band camp, KaalH! said:
>
>
>>Stephen Gran a ecrit :
>>
>>
>>>This one time, at band camp, KaalH! said:
>>>
>>>
you may use "/usr/bin/freshclam --quiet" instead of "
/usr/bin/freshclam /dev/null" within cron script.
This one time, at band camp, KaalH! said:
> Stephen Gran a ecrit :
> > This one time, at band camp, KaalH! said:
> > > you may use "/usr/bin/freshclam --quiet" instead of "
> > > /usr/bin/freshclam /dev/null" within cron script.
> >
> > No, that will miss warning messages. This decision
Stephen Gran a écrit :
This one time, at band camp, KaalH! said:
you may use "/usr/bin/freshclam --quiet" instead of " /usr/bin/freshclam
/dev/null" within cron script.
No, that will miss warning messages. This decision was made on purpose.
Is th
This one time, at band camp, KaalH! said:
> you may use "/usr/bin/freshclam --quiet" instead of " /usr/bin/freshclam
> > /dev/null" within cron script.
No, that will miss warning messages. This decision was made on purpose.
Is there a reason you want it changed?
--
6 matches
Mail list logo
