Hello!
>>>[...]
>>>PS: Use $OTRS_HOME/bin/Cron.sh {start|stop|restart} (as OTRS user) to
>>>start/stop this cronjobs from var/cron/*. The SuSE and Red Hat rc-script
>>>is doing this automatically.
>>>
>>I did that, but the probelm wasn't solved. I fixed a Syntax Error in my
>>additions and th
Hi Hannes,
On Tue, Oct 01, 2002 at 11:55:55PM +0200, Hannes Lau wrote:
> > [...]
> >PS: Use $OTRS_HOME/bin/Cron.sh {start|stop|restart} (as OTRS user) to
> >start/stop this cronjobs from var/cron/*. The SuSE and Red Hat rc-script
> >is doing this automatically.
> >
> I did that, but the probel
Hello Martin!
[...]
The cronjob is "var/cron/unlock".
And how does my System know about it? There was no instruction in the
/opt/OpenTRS/INSTALLATION to move it to my cronjobs directory or file or
whatever. Whether root nor infosys nor otrs have this job, displaying it by
crontab -u usernam
Hi Hannes,
On Tue, Oct 01, 2002 at 08:54:46AM +0200, Hannes Lau wrote:
> > [...]
> >The cronjob is "var/cron/unlock".
> >
> And how does my System know about it? There was no instruction in the
> /opt/OpenTRS/INSTALLATION to move it to my cronjobs directory or file or
> whatever. Whether root n
Hi Martin!
>>>Ok, if you do this this way, just change:
>>> To => '[EMAIL PROTECTED], '.$UserData{UserEmail},
>>>
>>:-) Thats exatly what i did. I modified the History entry too...
>>My Problem is another one. The Tickets are not unlocked by the system.
>>No Error Message, No History E
