Ok, thanks all. I’ll give it a try. Phil
> On Apr 25, 2020, at 3:53 PM, Marius Wikstøl <[email protected]> wrote: > > > Err, that -p is supposed to be a -g. > > Mvh > Marius > On 4/26/20 12:50 AM, Marius Wikstøl wrote: >> I do this in crontab (crontab -e) like this. >> >>> # if rivendell daemons are running, create the next days log if it doesn't >>> already exist >>> 0 2 * * * [ "`systemctl is-active rivendell`" == "active" ] && >>> /usr/local/bin/rdlogmanager -g -t -P -s Production >> It creates the next day's log at 2 am (if it doesn't already exist) so it's >> always a day ahead. Works like a charm. >> My installation (rdlogmanager) is under /usr/local/bin, but yours might be >> in /usr/bin >> >> -p - generate log >> -t - merge traffic >> -P don't overwrite existing log >> -s <service> >> >> Mvh >> Marius >> On 4/25/20 9:34 PM, Phil Biehl wrote: >>> I have logs working more or less correctly in RDAirplay but I seem to have >>> a problem. When the log runs to the chain event to the next days log, it >>> fails and RDAirplay stops because there is no log to chain to. If there is >>> a log then all is well. How are log automatically generated? Any ideas why >>> it isn’t getting generated? >>> >>> Thanks all,Phil >>> >>> >>> >>> >>> _______________________________________________ >>> Rivendell-dev mailing list >>> [email protected] >>> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
_______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
