Fast Uncompromising Discussions. FUDforum will get your users talking.
Logout [ CommonCrawl [Bot] ]
Logged in user:
CommonCrawl [Bot] [
list all smilies
Editing Time Limit
[quote title=naudefj wrote on Thu, 16 December 2010 05:20]Yes, that sounds like bad advice. PS: The "science" behind "shebang" lines is not FUDforum specific, you can read more about it at [url]http://en.wikipedia.org/wiki/Shebang_(Unix)[/url] [/quote]
Allowed File Extensions:
jpg jpeg png gif txt doc gz bz2 inc php zip diff
Maximum File Size:
Maximum Files Per Message:
Notify me when someone replies to this message.
Include your profile signature.
Disable smilies in this message
Re: cron jobs and "shebang" lines
Thu, 16 December 2010 05:20
Yes, that sounds like bad advice.
PS: The "science" behind "shebang" lines is not FUDforum specific, you can read more about it at
cron jobs and "shebang" lines
Tue, 14 December 2010 21:39
The FUDforum documentation says that certain php files require what is called a "shebang" line as the first line in the code. These begin #! and then refer to the location of the php binary [something].
Faithfully, I have always tried to follow this. However, my host provider is telling me something different for situations when a file is executed through a cron job. They write,
"Also please keep in mind, that each script that you want to run via cron should be chmoded to 755 permissions and you should remove #![shebang line] in the beginning of each script."
Curiously, when I ran the xml aggregation rule, it seemed to work the same even though the shebang line was excluded. It did not seem to matter. However, when I tried to pipe mail, I had all sorts of fatal errors that killed the operation.
Putting aside the issue of why there is different results, I take it that my host is wrong about the advice to take out the shebang lines? And I should ignore the advice?
Sat Apr 10 14:35:42 EDT 2021
Total time taken to generate the page: 0.00642 seconds
Powered by: FUDforum 3.1.0.
FUDforum Bulletin Board Software