I want to run a shell script upon system shutdown in Knoppix Live (which runs from a writable USB flash drive) so that I can backup some data and ftp it to a remote server. The script works fine but I'm not sure where to put it so that it executes when the system goes into shutdown.
I want to automatically run a script whenever new files are copied into a particular directory. In other words, is there a way in Linux to "watch" a directory for changes and then run something in response to the change?
I just installed Debian 5 (Lenny) and I noticed that /lib/init/rw is reported as a RAM Disk (tmpfs). I've only had experience with Fedora so I'm curious what function does that directory serve in Debian. Can it be used by user written shell scripts to cache stuff or is it off-limits and only for use by the OS? Thanks.
I'll like to know what are the things to consider when choosing between configuring an app as static or as dynamic in an Apache 2 server that uses mod_fastcgi. The app is a typical reporting app written in Perl with MySQL as the Db backend with fairly medium traffic. I'll love to hear your experiences about running FastCGI in such a scenario.
This is a very old FastCGI issue but I have never found a satisfactory answer.
Searching the phrase "(13) permission denied fastcgi can't create server" on Google will show that there's a lot of people experiencing this issue for a long while.
Some people blame it on selinux and suggest turning it off (not acceptable solution).
Other people think that it's a strange symlink permissions problem and suggest turning the Apache logs directory from symlink to a plain directory. (not acceptable, since it involves moving the logs files) See Installing FastCGI.
Below is the dreaded error as typically logged by Apache.
[Wed Jun 14 22:09:34 2009] [notice] Apache/2.0.40> (Red Hat Linux) configured
-- resuming normal operations
[Wed Jun 14 22:09:35 2009] [crit] (13)Permission
denied: FastCGI: can't create server "/var/rt3/bin/mason_handler.fcgi": bind()
failed [/etc/httpd/logs/fastcgi/70d9a528c5892f2bf0c25e5a334bed81]
Hoping serverfault can finally provide a definitive answer to this perplexing and annoying problem which has plague FastCGI users for years.
I feel uneasy implementing the suggested "cures" when no one really knows the underlying cause of this illness. Hope to get to the bottom of this mystery.