Timeout for pending tickets
Hi,
I want to change the default timeout for pending tickets, i.e. currently
the preselected timeout is 24 hours when I select "pending auto-close".
I vaguely recall having seen this option somewhere last year, but can't
find it right now anymore :-/
TIA for any pointers,
--
Daniel Seifert
On Tuesday, March 16, 2004 9:04 PM
Daniel Seifert
I want to change the default timeout for pending tickets, i.e. currently the preselected timeout is 24 hours when I select "pending auto-close". I vaguely recall having seen this option somewhere last year, but can't find it right now anymore :-/
You're searching for this: # PendingDiffTime # (Time in sec. which "pending date" shows per default) [default: 24*60*60 -=> 1d] $Self->{PendingDiffTime} = 24*60*60; hth, Robert Kehl -- ((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg http://www.otrs.de/ :: Tel. +49 (0)6172 4832388
Hi,
after applying the change in Config.pm I had to restart OTRS to have it
take effect. It worked great, but the restart-force modified the file
permissions. bin/PostMaster.pl lost its "x" (took me some hours to get
suspicious why nobody wanted support today ;-)). I experienced this
before but wasn't able to reproduce it after the update, so I thought
this was gone for good.
--
Daniel Seifert
On Wednesday, March 17, 2004 11:08 PM
Daniel Seifert
after applying the change in Config.pm I had to restart OTRS to have it take effect. It worked great, but the restart-force modified the file permissions. bin/PostMaster.pl lost its "x" (took me some hours to get suspicious why nobody wanted support today ;-)). I experienced this before but wasn't able to reproduce it after the update, so I thought this was gone for good.
Yes, a rcotrs stop does indeed change the permissions of to 644, to disable it. Thus a stop-force does the same. A subsequent start(-force) should enable it again by setting it back to 755 and telling you so. Didn't you receive a message about the changes? You should have - two times. Under which user account did you execute 'rcotrs'? You can view the status not only of PostMaster.pl at any time via 'rcotrs status'. Fröhlich grüßt Robert Kehl -- Die Achillesferse von Bobic ist die rechte Schulter. Gerd Rubenbauer
Am Mi, den 17.03.2004 schrieb Robert Kehl um 23:29: Hi,
Yes, a rcotrs stop does indeed change the permissions of to 644, to disable it.
Uh, wouldn't it be better to just have a small check in PostMaster.pl to see whether OTRS is still running or not? Like a lockfile?
Thus a stop-force does the same. A subsequent start(-force) should enable it again by setting it back to 755 and telling you so.
Didn't you receive a message about the changes? You should have - two
I see. Apparently the problem is that starting mysql on my SuSE Linux 9.0 box (I remember having this problem on SuSE Linux 8.1 as well) does return an error (though the database is up and running fine[1]), interrupting the start-force of OTRS. [1] The mysql start script checks the result of "/usr/bin/mysqladmin ping" but this command returns "error: 'Access denied for user: 'root@localhost' (Using password: NO)'".
times. Under which user account did you execute 'rcotrs'?
root. As user OTRS I don't have the permissions to restart apache/mysql.
--
Daniel Seifert
On Thursday, March 18, 2004 8:25 AM
Daniel Seifert
Yes, a rcotrs stop does indeed change the permissions of to 644, to disable it.
Uh, wouldn't it be better to just have a small check in PostMaster.pl to see whether OTRS is still running or not? Like a lockfile?
Yes, one could think about this. Good idea.
Thus a stop-force does the same. A subsequent start(-force) should enable it again by setting it back to 755 and telling you so.
Didn't you receive a message about the changes? You should have - two
I see. Apparently the problem is that starting mysql on my SuSE Linux 9.0 box (I remember having this problem on SuSE Linux 8.1 as well) does return an error (though the database is up and running fine[1]), interrupting the start-force of OTRS.
[1] The mysql start script checks the result of "/usr/bin/mysqladmin ping" but this command returns "error: 'Access denied for user: 'root@localhost' (Using password: NO)'".
So you changed the password for root@localhost - brave. You'll have to configure the mysql startup script to use another account that is allowed to ping mysql from localhost. Unfortunately, I cannot tell you where to do so... hth, Robert Kehl -- ((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg http://www.otrs.de/ :: Tel. +49 (0)6172 4832388
Am Do, den 18.03.2004 schrieb Robert Kehl um 14:24: Hi,
[1] The mysql start script checks the result of "/usr/bin/mysqladmin ping" but this command returns "error: 'Access denied for user: 'root@localhost' (Using password: NO)'".
So you changed the password for root@localhost - brave. You'll have to
I tend to think that this was a recommendation to set a password, at least I think so ;)
configure the mysql startup script to use another account that is allowed to ping mysql from localhost. Unfortunately, I cannot tell you where to do so...
OK, I'll check the docs for mySQL. In the meantime I've modified the
start scripts ;)
--
Daniel Seifert
participants (2)
-
Daniel Seifert -
Robert Kehl