Re: [Slackbuilds-users] Cron file included with clamav-unofficial-sigs seems broken/incompatible with Slackware

On 10/19/2016 08:41 AM, Franzen wrote: On 19.10.2016 12:17, Sebastian Arcus wrote: On 19/10/16 10:59, Franzen wrote: On 19.10.2016 11:42, Sebastian Arcus wrote: The clamav-unofficial-sigs.cron crond crontab file included with clamav-unofficial-sigs seems to be incompatible with the version of

Re: [Slackbuilds-users] Cron file included with clamav-unofficial-sigs seems broken/incompatible with Slackware

On 20.10.2016 11:25, B Watson wrote: On 10/19/16, Nishant Limbachia wrote: Here's my crontab (root) # Run clamav-unofficial-sigs script 6 * * * * /usr/bin/bash /usr/bin/clamav-unofficial-sigs.sh > /dev/null Why is this incompatible with slackware? That's the

Re: [Slackbuilds-users] Cron file included with clamav-unofficial-sigs seems broken/incompatible with Slackware

On 10/19/16, Nishant Limbachia wrote: > Here's my crontab (root) > > # Run clamav-unofficial-sigs script > 6 * * * * /usr/bin/bash /usr/bin/clamav-unofficial-sigs.sh > /dev/null Why is this incompatible with slackware? /usr/bin/ is a weird place to look for bash, but my

Re: [Slackbuilds-users] Cron file included with clamav-unofficial-sigs seems broken/incompatible with Slackware

I'm still not sure I'm following this: why is the cron file provided with the Slackbuilds at all, if it is incompatible with Slackware? It's worse than nothing - as the user would copy it in place and assume it works - as it comes from Slackbuilds and it is presumed to be tested to work with

Re: [Slackbuilds-users] Cron file included with clamav-unofficial-sigs seems broken/incompatible with Slackware

On 19/10/16 21:26, Nishant Limbachia wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 10/19/2016 08:41 AM, Franzen wrote: On 19.10.2016 12:17, Sebastian Arcus wrote: On 19/10/16 10:59, Franzen wrote: On 19.10.2016 11:42, Sebastian Arcus wrote: The clamav-unofficial-sigs.cron crond

Re: [Slackbuilds-users] Cron file included with clamav-unofficial-sigs seems broken/incompatible with Slackware

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 10/19/2016 08:41 AM, Franzen wrote: > On 19.10.2016 12:17, Sebastian Arcus wrote: >> On 19/10/16 10:59, Franzen wrote: >>> On 19.10.2016 11:42, Sebastian Arcus wrote: The clamav-unofficial-sigs.cron crond crontab file included with

Re: [Slackbuilds-users] Cron file included with clamav-unofficial-sigs seems broken/incompatible with Slackware

On 19.10.2016 12:17, Sebastian Arcus wrote: On 19/10/16 10:59, Franzen wrote: On 19.10.2016 11:42, Sebastian Arcus wrote: The clamav-unofficial-sigs.cron crond crontab file included with clamav-unofficial-sigs seems to be incompatible with the version of Cron used on Slackware. It uses the

Re: [Slackbuilds-users] Cron file included with clamav-unofficial-sigs seems broken/incompatible with Slackware

On 19/10/16 10:59, Franzen wrote: On 19.10.2016 11:42, Sebastian Arcus wrote: The clamav-unofficial-sigs.cron crond crontab file included with clamav-unofficial-sigs seems to be incompatible with the version of Cron used on Slackware. It uses the extra field for the username (clamav) which

Re: [Slackbuilds-users] Cron file included with clamav-unofficial-sigs seems broken/incompatible with Slackware

On 19.10.2016 11:42, Sebastian Arcus wrote: The clamav-unofficial-sigs.cron crond crontab file included with clamav-unofficial-sigs seems to be incompatible with the version of Cron used on Slackware. It uses the extra field for the username (clamav) which seems to break things on Slackware.

[Slackbuilds-users] Cron file included with clamav-unofficial-sigs seems broken/incompatible with Slackware

The clamav-unofficial-sigs.cron crond crontab file included with clamav-unofficial-sigs seems to be incompatible with the version of Cron used on Slackware. It uses the extra field for the username (clamav) which seems to break things on Slackware. I've just noticed this on several clamav