Alex Future Bokov says:
...
> # each time it runs. Toss it into your crontab or .login. Add some words of
> # your own. Have fun!
> #
> # Warning: It will blow away any existing .sig file, so back 'em up!
...
> $egreeting <<EOF;
You have a syntax error here.
It should be:
$egreeting =<<EOF;
It doesn't compile otherwise.
Also, if you're on a Unix system, you can make your .signature a fifo
using mkfifo, and you can keep this program running nohup by writing a
loop around it to keep it writing to the .sig file and closing after
each write. This way each fresh read will get a fresh run.
The loop could look basically like this:
while(1)
{
open (">/path/to/.sig") or die "Could not open .sig: $!";
# do the rest of the program here
# ...
# be sure to close
close SIG or die "Got an error closing .sig: $!";
}
Note that I've added error checking to both system calls. Always
check the return value from system calls.
Now, then, after you mkfifo .sig, all you need to do is execute the
program nohup:
nohup sigwriter &
And any read will get a fresh set of words. If you want, you can put
a monitor job in your crontab or login to make sure it's still running
every now and then. The best way would be to have it record its
process id on startup in a file you check for an extand pid by the
same process name.
All the best,
James
This archive was generated by hypermail 2b29 : Mon Oct 02 2000 - 17:35:42 MDT