Am So, den 09.05.2004 schrieb Robert Kehl um 20:05: Hi,
> > Ack. What we's need were the whole history of the offending ticket > > alongside its contents. May you forward a mitigated version to me via > > PM alongside any additional information that weren't suited for a > > public ML. > > After reviewing the history you sent I must say I cannot draw a line > between the lockout and neither 5000 nor 7000 hours. It's not obvious, > why it gets unlocked. > > What happens at the time of unlocking, ie. which script runs at that > time? It may well be a GenericAgent job unlocks the ticket, aside any > automatic unlock time. $ cat ~otrs/var/cron/unlock 35 * * * * $HOME/bin/UnlockTickets.pl --timeout >> /dev/null This was set by the OTRS rpm default installation and the unlock time matches the cron-job run time. So I guess it's a bug in UnlockTickets.pl -- Daniel Seifert <[EMAIL PROTECTED]> _______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs Support oder Consulting für Ihr OTRS System? => http://www.otrs.de/
