Hello all!
I'd like to allow multiple software groups within our single
organization to handle their own "issue reporting" via OTRS. Since I
don't want to manage multiple servers, and want them each to have full
administrative control over their own FAQ entries, customer users, etc
-- I had planned on installing multiple OTRS installations like this:
ScriptAlias /otrs1/ /local/otrs1
ScriptAlias /otrs2/ /local/otrs2
(and so on...)
Problem is, I'm running into wierd behaviors with the secondary and
other OTRS's. Log.pm seems to use the OTRS ID as a function for
grabbing memory for logging. Is that true? If I set my server IDs "1"
and "2" then #2 has memory conflicts, but if I set them to "1" and "20"
then it seems fine.
Has anyone done this before, and does anyone know how to accomplish it
better, perhaps?
--
-------------------------------------------------------------
Matt Linton "So, you think there's no money
UNIX/Linux SysAdmin to be made as a philosophy major?
ASANI Solutions, LLC Think again! You're still right."
_______________________________________________
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/
