I have read the manual, and looked at the archives and even noticed someone
was having the same problem recently with RedHat version 7.2.

I have the web interface up and running.  In the /opt/OpenTRS/scripts/ there
is a file redhat-rcotrs.  Just by looking at the file, it appears that this
file is the starup script for the otrs.  In comparing this file with the
suse-rcotrs file, there are several directives missing, cleanup, stop-force,
etc.

While I know that OpenTRS was not developed with Redhat specifically in
mind, can anyone point me in the direction to try to make it work under
RedHat 7.3.  I would be more than happy to write a FAQ for RedHat.  I just
need an understanding of how OpenTRS works.

Here are the messages that I am getting.


      From: [EMAIL PROTECTED] (Cron Daemon)
      To: [EMAIL PROTECTED]
      Date: Sat, August 24, 2002 8:30 am
      Subject: Cron <otrs@eve> $HOME/bin/UnlockTickets.pl --timeout >>
/dev/null

----------------------------------------------------------------------------
----

        (in cleanup) Can't call method "disconnect" on an undefined value at
/opt/OpenTRS/bin/..//Kernel/System/DB.pm line 93 during global destruction.
From: [EMAIL PROTECTED] (Cron Daemon) To:
[EMAIL PROTECTED] Date: Sat, August 24, 2002 8:00 am Subject: Cron
<otrs@eve> /etc/rc.d/otrs cleanup >>
/dev/null ------------------------------------------------------------------
--------------/bin/sh: /etc/rc.d/otrs: No such file or directory
Sincerely,Adrian McCray
_______________________________________________
OpenTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

Reply via email to