Hi, are existing some tools to manage the otrs data base scheme? thanks in advance Denis
Hi Denis, On Mo, Jul 04, 2005 at 05:49:23 +0200, Denis Julien wrote:
are existing some tools to manage the otrs data base scheme?
You can use either the OTRS web frontend or the client programm of your database server, e.g. any mysql client. But normaly you don't have to access the database directly with the client... Refering to your question in the subject of this mail I'd like to say, that OTRS isn't designed to delete users, customers, queues, e.g. You can only mark them "invalid" in the specific area of the web frontend. The reason for this is, that deleting users, customers, e.g. could cause data inconsistency. OTRS won't longer work properly, if a user is deleted but there are still tickets, that were created by this user...
Denis
Kind regards, Christian -- ((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg http://www.otrs.de/ :: Manage your communication!
Good Morning Is it possilbe to setup one user who's session does not time out or perhaps is there a way that we can authenticate a user in the url e.g. http://user:pwd@otrs.server.co.za? Thanks Rudi
Rudi Kramer wrote:
Good Morning
Is it possilbe to setup one user who's session does not time out or perhaps is there a way that we can authenticate a user in the url e.g. http://user:pwd@otrs.server.co.za?
Thanks Rudi
Making the session not timeout would probably be difficult, but setting it to a very large timeout is easy. In Kernel/Config.pm: $Self->{SessionMaxTime} = 60 * 60 * 24 * 365; # one year is enough $Self->{SessionMaxIdleTime} = 60 * 60 * 24 * 365; # one year is enough
Thanks for the info, I would only like to give one user a unlimited Session
time out, is this possible?
Rudi
----- Original Message -----
From: "Jeremy Blain"
Rudi Kramer wrote:
Good Morning
Is it possilbe to setup one user who's session does not time out or perhaps is there a way that we can authenticate a user in the url e.g. http://user:pwd@otrs.server.co.za?
Thanks Rudi
Making the session not timeout would probably be difficult, but setting it to a very large timeout is easy.
In Kernel/Config.pm:
$Self->{SessionMaxTime} = 60 * 60 * 24 * 365; # one year is enough $Self->{SessionMaxIdleTime} = 60 * 60 * 24 * 365; # one year is enough
_______________________________________________ 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/
participants (4)
-
Christian Schoepplein -
Denis Julien -
Jeremy Blain -
Rudi Kramer