ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
There's a much better way to get a date string than shelling out to the date command... See the manual page for the Date::Format module.
Thanks for replying. The script above is to test a concept. The actual bash script will contain several commands which may need to write to a log file. If I don't write the part ">> <file>", the date shows in the response page. But if I add that part, I expect the date to be written into the file.
When you use exec() to launch your bash script, the perl script terminates. If you really want to do it this way (and I can't imagine why you would ever want to drop to a bash script from perl), you can either fork() a child process to launch the shell script, or use the system() perl command, use the `backtick` format of the command, or...
Probably, your cgi-bin directory is [correctly] configured with permissions disallowing writes by the web server. To allow Write-Execute permission would be a security issue. Use a directory with no execute permission.
--- rod.
Probably, your cgi-bin directory is [correctly] configured with permissions disallowing writes by the web server. To allow Write-Execute permission would be a security issue. Use a directory with no execute permission.
--- rod.
Thanks theNbomr.
No more BASH in my scripts, just PERL.
You were right, Apache was running as "apache", and the log files in /var/log/* were showing write permission errors.
Getting the script to work is a matter of setting the right permissions.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.