Hi Thomas,
On Wed, Nov 20, 2002 at 02:59:59PM +0100, Thomas Schuettler wrote:
> here more about the problem. Before the passwords change, there is a
> problem with apache.
> From error.log:
> #
> [Wed Nov 20 16:35:10 2002] [error
Hi all,
Here in Technets the OTRS is becoming the "killer app" for the customer
support, we are very happy with the app, and we can start to ask some
features to the development team:
The most requested feature from the customer support team is the possibility
to add to the responses some "standar
Hi Bryan,
On Thu, Nov 21, 2002 at 07:59:21AM -0500, Bryan Fullerton wrote:
> >In $OTRS_HOME/var/cron/* are all cron jobs for the otrs user located.
> >
> >Its better to do the changes there, because on the next
> >otrs-cron-reload
> >(bin/Cron.sh start) your changes of (crontab -e otrs...) are lo
Hi Jon,
On Thu, Nov 21, 2002 at 10:14:27AM -0600, Jon Conkle wrote:
> Okay, i created user otrs before i installed OTRS. However, for some
> reason a home directory was never created for that user (i never noticed
> until now). So i assume that when OTRS is installing, it's supposed to
> cop
Okay, i created user otrs before i installed OTRS. However, for some
reason a home directory was never created for that user (i never noticed
until now). So i assume that when OTRS is installing, it's supposed to
copy a bunch of stuff into that home directory? that's the problem?
if so, do
On Thursday, November 21, 2002, at 01:30 AM, Martin Edenhofer wrote:
In $OTRS_HOME/var/cron/* are all cron jobs for the otrs user located.
Its better to do the changes there, because on the next
otrs-cron-reload
(bin/Cron.sh start) your changes of (crontab -e otrs...) are lost.
Aren't the fil
