Thanks for the input. Actually, I am using 2.0 on Solaris for the moment. I put in a hack to get around the SysLog problem and things seem to be working as expected, based on the comments from the development threads.
I'll document what I'm doing as an "out of the box" Solaris 10 installation (including setting up the appropriate links for the compilers, etc) on the O/S and continue documenting my experiences with the Solaris installation. When I'm finished, I'll send you all the information that I have and perhaps it will be useful to include the differences as an addendum to the documentation. Thanks again for the info. Bernie Frye -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christian Schoepplein Sent: Monday, May 23, 2005 12:36 PM To: Development community of OTRS.org Subject: Re: [dev] OTRS on Solaris X86 Hello! First of all I have to mension, that I'm no solaris expert ;-). On Mo, Mai 23, 2005 at 11:43:52 -0400, Frye, Bernie wrote: > Has anyone loaded OTRS 1.32 or higher on Solaris X86 platforms with > reasonable success? I'm running into some interesting issues getting it > to run successfully and I noticed that the bulk of the documentation is > written for Linux type platforms. I am running our production server on > Linux but am considering changing to Solaris due to database size > advantages and speed advantages. > > > > Right now I'm getting an error that the System Log is failing on > connecting to a TCP socket connection to SysLog.pm. This only happens on > the Solaris platform and not the Linux platform. I am willing to admit > that it could be setup problems specific to the Solaris environment, but > it would still be nice to have more generic Unix documentation. ACK. If you had successfully setuped your system on solaris, we'd be very interested in your experiences ;-). I don't know, how syslogin is done on solaris, but you could try to switch the loginmode of OTRS from syslog to a plain logfile. Just set the following parameters in Kernel/Config.pm (for OTRS 2.0): $Self->{LogModule::LogFile} = '/tmp/otrs.log'; $Self->{LogModule} = 'Kernel::System::Log::File'; I'd recomment to use OTRS 2.0 even it is still beta, because this version has many new features and ofcourse we develop and fix bugs for 2.0 with a higher priority than 1.3.x. Best regards, Christian -- ((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg http://www.otrs.de/ :: Manage your communication! _______________________________________________ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev _______________________________________________ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
