And why is Importance only low?
A logfile analyzer which not runs to the right time is not really
useful.
So can please somebody change the Importance to more than low or still
fix it (it is not so mush to do).
** Changed in: sarg (Ubuntu)
Status: In Progress => Confirmed
--
You receiv
still no fix on the package?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/239384
Title:
Sarg cron scripts don't generate logs correctly
To manage notifications about this bug go to:
https://bugs.l
>From my POV, the user argument is missing. It should look like this:
SHELL=/bin/sh
PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
00 08-18/1 * * * root sarg-reports today
00 00 * * * root sarg-reports daily
00 01 * * 1 root sarg-reports weekly
30 02 1 * * root sarg-reports m
** Changed in: sarg (Ubuntu)
Importance: Undecided => Low
** Changed in: sarg (Ubuntu)
Status: Confirmed => In Progress
** Changed in: sarg (Ubuntu)
Assignee: (unassigned) => Andrea Colangelo (warp10)
--
Sarg cron scripts don't generate logs correctly
https://bugs.launchpad.net/b
this bug is present since 2 years
** Changed in: sarg (Ubuntu)
Status: New => Confirmed
--
Sarg cron scripts don't generate logs correctly
https://bugs.launchpad.net/bugs/239384
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
always present in Lucid
way to solve :
rm /etc/cron.daily/sarg
rm /etc/cron.weekly/sarg
rm /etc/cron.monthly/sarg
echo "PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
00 08-18/1 * * * sarg-reports today
00 00 * * * sarg-reports daily
00 01 * * 1 sarg-reports weekly
