bin/Cron.sh looks at otrs/var/cron for files without .dist attached and makes them be your crontab. It is possible that it runs itself.
On Mon, Jul 16, 2012 at 10:43 AM, Derek Kiely <[email protected]>wrote: > Hi All,**** > > ** ** > > I recently migrated from 2.4.4 to 3.1.7 (3.0.1 in the middle) and since > upgrading, I am having problems with my cron jobs,**** > > ** ** > > Bascally my crontab looks like this **** > > ** ** > > 01 01 * * * $HOME/bin/RebuildTicketIndex.pl >> /dev/null**** > > ** ** > > When it should look like**** > > ** ** > > 01 01 * * * $HOME/bin/otrs.RebuildTicketIndex.pl >> /dev/null**** > > ** ** > > I have edited all the files in /opt/otrs/var/cron including .dist files to > reflect the right values but when I came in again today the problem was > back again. During my upgrade I had some .rpmnew files created that had the > right information in them but they did no overwrite the existing files. > These files were again created today so it looks like something is running > that is recreating these files or adjusting the old files.**** > > ** ** > > Any idea what could be overwriting these scripts? **** > > ** ** > > Derek Kiely**** > > ** ** > > --------------------------------------------------------------------- > 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 >
--------------------------------------------------------------------- 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
