seg fault / mem fault - in cron, but works in shell?
Strange problem --
A detailed shell script in ksh which calls a specific program works just fine when run interactively. Now, if you run this same program in cron, it seg faults!
Yes, I have resolved all issues of environment with the sh vs ksh inside of cron. The irony is even with #!/bin/ksh in the script AND forcing it with a /bin/ksh on the crontab entry the program still does a memory fault. If I let it try to execute under default of /bin/sh, it does a seg fault. But the program works flawlessly if you execute the script in an interactive session.
1. there are no inputs other than reading from files and writing to database.
2. the only difference is a cron entry vs. ./script_name
What could be causing this? Any thoughts or ideas?
AS 4 - updated with all patches. vixie_cron 4.1.x, so I am at my wits end on this.
Please post your thread in only one forum. Posting a single thread in the most relevant forum will make it easier for members to help you and will keep the discussion in one place. This thread is being closed because it is a duplicate.
|All times are GMT -5. The time now is 02:49 AM.|