I also have never had this problem and we use "hard" time events all the time.
I have had (and still do) problems with, at least macro events, that are too
short (time wise) that things can be skipped over, but that doesn't seem to be
your case either.
Other places to look for hints to what is going on is:
1) Generate an "as played" log, as in setup a log that records all events,
(in rdadmin), then go and generate one of them (in rdlogmanager) for a day you
had problems. It will produce a simple text file somewhere that you can easily
share with us.
2) Logs of Rivendell events show up in system logs anyway. Depending on
your Linux Distribution, it should show up a few places so try these commands
and see what you find:
a. sudo less -S /var/log/syslog
b. sudo less -S /var/log/messages
and look for various "caed" events so to see what and when things are
happening. ("less" is a simple pager, you can use Pg-up/dn to navigate around
or "/<searchtext>" to search for things, "//" does a "search next". Do "man
less" for more info.)
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
