Cron is sending me an error:
error: gpg required but not found! It is not recommended, but you can use
sa-update with the --no-gpg to skip the verification.
However, if I run sa-update -D from the command line, it succeeds:
Feb 4 08:48:26.885 [48573] dbg: logger: adding facilities: all
Feb
Perhaps /usr/local/bin is not on PATH for the cron user?
On 2/4/2015 10:50 AM, LuKreme wrote:
Cron is sending me an error:
error: gpg required but not found! It is not recommended, but you can use
sa-update with the --no-gpg to skip the verification.
However, if I run sa-update -D from the
On Wed, 4 Feb 2015, LuKreme wrote:
On Feb 4, 2015, at 8:57 AM, Joe Quinn jqu...@pccc.com wrote:
Perhaps /usr/local/bin is not on PATH for the cron user?
I don’t understand what you are saying. The crontab lists the full path.
# crontab -l |grep sa-update
16 1 * * *
On Feb 4, 2015, at 8:34 PM, David B Funk dbf...@engineering.uiowa.edu wrote:
On Wed, 4 Feb 2015, LuKreme wrote:
On Feb 4, 2015, at 8:57 AM, Joe Quinn jqu...@pccc.com wrote:
Perhaps /usr/local/bin is not on PATH for the cron user?
I don’t understand what you are saying. The crontab
On Feb 4, 2015, at 8:57 AM, Joe Quinn jqu...@pccc.com wrote:
Perhaps /usr/local/bin is not on PATH for the cron user?
I don’t understand what you are saying. The crontab lists the full path.
# crontab -l |grep sa-update
16 1 * * * /usr/local/bin/sa-update /usr/local/bin/sa-compile
Our rules qa is currently corpora starved so we have not published rules since
Sunday, I believe.
Regards,
KAM
On February 3, 2015 9:47:41 PM EST, David Dodell da...@d2net.net wrote:
I have noticed that the last three nights that I have not had any rule
updates, sa-update exists with code 1.
Tim Taylor wrote:
For the last few days (from 31 Jan 2015), sa-update has been failing on
my
server. I've checked and can't see that any package updates happened
around
then, so I'm puzzled by why this is happening (it's been working fine
for
over a year beforehand).
I'm running sa-update
Hi Mark,
Thanks very much - you were spot on! I had noticed the file there, but
didn't think it was unusual. But I've now deleted the file (along the the
associated .asc and .sha1 files which were also there), and sa-update now
works again.
Many thanks for your help.
On Wed, Feb 4, 2015 at
hi-
i happened to notice a bunch of old files in /tmp/, related to
spamassassin. after a bit of testing, it looks like sa-compile isn't
cleaning up after itself?
ls -alH /tmp/
total 44
drwxrwxrwt 2 root root 36864 Feb 3 17:18 .
drwxr-xr-x 22 root root 4096 Dec 25 00:34 ..
sa-compile
For the last few days (from 31 Jan 2015), sa-update has been failing on my
server. I've checked and can't see that any package updates happened around
then, so I'm puzzled by why this is happening (it's been working fine for
over a year beforehand).
I'm running sa-update version svn1475932 (with
Define your path in the cron script.
LuKreme krem...@kreme.com wrote:
On Feb 4, 2015, at 8:34 PM, David B Funk
dbf...@engineering.uiowa.edu wrote:
On Wed, 4 Feb 2015, LuKreme wrote:
On Feb 4, 2015, at 8:57 AM, Joe Quinn jqu...@pccc.com wrote:
Perhaps /usr/local/bin is not on PATH for the
On Feb 4, 2015, at 9:21 PM, Kevin A. McGrail kmcgr...@pccc.com wrote:
Define your path in the cron script.
The front actin simply calls sa-update. Do I just
16 1 * * * PATH=/usr/bin:/bin:/usr/local/bin /usr/local/bin/sa-update
/usr/local/bin/sa-compile /usr/local/etc/rc.d/sa-spamd
12 matches
Mail list logo
