Hello, I have a queue where unlock time is set 1, I understand this means that holding time is one minute, and thne that message is unlocked. But this works only with the cronjob changed from 35 * * * * $HOME/bin/UnlockTickets.pl --timeout >> /dev/null to 35 * * * * $HOME/bin/UnlockTickets.pl --all >> /dev/null Queues with unlock time set to 0, are not affected and the tickets are not unlocked, even with the all option. Is that the planned behaviour? Thanks Christoph
Hi Christoph, On Wed, Feb 19, 2003 at 11:16:30AM +0100, Christoph Kaulich wrote:
I have a queue where unlock time is set 1, I understand this means that holding time is one minute, and thne that message is unlocked.
But this works only with the cronjob changed from
35 * * * * $HOME/bin/UnlockTickets.pl --timeout >> /dev/null [...]
This "UnlockTickets.pl --timeout" cronjob runs every hour. -=> Every hour is a little bit bad for 1 min unlocks. --=> You need to run the cronjob every 2 min (or something like that).
35 * * * * $HOME/bin/UnlockTickets.pl --all >> /dev/null
Queues with unlock time set to 0, are not affected and the tickets are not unlocked, even with the all option.
Is that the planned behaviour?
No. If you use "UnlockTickets.pl --all" _all_ locked tickets in the system should be unlocked.
Christoph
Martin -- Martin Edenhofer - <martin at edenhofer.de> - http://martin.edenhofer.de/ -- Old programmers never die. They just branch to a new address.
Hi Martin, Martin Edenhofer wrote:
Hi Christoph,
On Wed, Feb 19, 2003 at 11:16:30AM +0100, Christoph Kaulich wrote:
I have a queue where unlock time is set 1, I understand this means that holding time is one minute, and thne that message is unlocked.
But this works only with the cronjob changed from
35 * * * * $HOME/bin/UnlockTickets.pl --timeout >> /dev/null [...]
This "UnlockTickets.pl --timeout" cronjob runs every hour. -=> Every hour is a little bit bad for 1 min unlocks. --=> You need to run the cronjob every 2 min (or something like that).
35 * * * * $HOME/bin/UnlockTickets.pl --all >> /dev/null
Queues with unlock time set to 0, are not affected and the tickets are not unlocked, even with the all option.
Is that the planned behaviour?
No. If you use "UnlockTickets.pl --all" _all_ locked tickets in the system should be unlocked.
but I have a queue with Unlock Time = 0 => No tickets are unlocked
and one queue with Unlock Time = 1 => All tickets are unlocked
and my cron job is
mucki - kaulich - /home/kaulich:
23 -> more /opt/otrs/var/cron/unlock
# --
# cron/unlock - unlock old locked ticket of the OTRS
# Copyright (C) 2002-2003 Martin Edenhofer
Christoph
Martin
-- Martin Edenhofer - <martin at edenhofer.de> - http://martin.edenhofer.de/ -- Old programmers never die. They just branch to a new address.
_______________________________________________ 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
Christoph
Hi Christoph, On Fri, Feb 21, 2003 at 08:08:46AM +0100, Christoph Kaulich wrote:
No. If you use "UnlockTickets.pl --all" _all_ locked tickets in the system should be unlocked.
but I have a queue with Unlock Time = 0 => No tickets are unlocked and one queue with Unlock Time = 1 => All tickets are unlocked
I tried the following on OTRS 1.0.1:
Queue 'test-session-raw' unlock time '0'. -=> Locked ticket (2003020610000194
with state open) -=> Ticket is locked and shown in AgentMailbox -=>
[...]
nohl:~ # /opt/otrs/bin/UnlockTickets.pl --all
UnlockTickets.pl
Christoph
Martin -- Martin Edenhofer - <martin at edenhofer.de> - http://martin.edenhofer.de/ -- Old programmers never die. They just branch to a new address.
participants (2)
-
Christoph Kaulich -
Martin Edenhofer