10 More Discussions You Might Find Interesting
1. UNIX for Beginners Questions & Answers
Hello,
I am running under ubuntu 14.04
Very long time ago, I set a script (ban.sh) to block ip addresses abusing my system which was not active.
I have not touched the server over six months or more.
Today, after restart the system, ban.sh started running all of a sudden and keep submitting... (4 Replies)
Discussion started by: baris35
4 Replies
2. Shell Programming and Scripting
Hii Friends,
I am using Perl CGI. I am running A SCP Command via Perl CGI in Background. Like
system("scp -r machinename:/PathOfFile/ /Path/WhereToCopyIt/ &)
This Copy Process takes some times lets say 15 min.
Now I want When This copy process gets complete then send me... (5 Replies)
Discussion started by: Navrattan Bansa
5 Replies
3. Shell Programming and Scripting
get email notification from from system when a process from XXXX user takes longer than 15 min run.Let me know the time estimation for the same.
hi ,any one please tell me , how to write a script to get email notification from system when a process from as mentioned above a xxxx user takes... (1 Reply)
Discussion started by: kirankrishna3
1 Replies
4. UNIX for Dummies Questions & Answers
Hey guys,
Just wondering is there anyway that I would be able to run a detached process that would continue to run regardless of me being logged into the linux host? (4 Replies)
Discussion started by: killaram
4 Replies
5. Shell Programming and Scripting
Hi all,
I am having a little bit of trouble trying to find something out. I am trying to script a start/stop php file, for some gaming servers i host. The server have 2 lots of processes running on them, and the customers need to be able to start and stop them at their will.
So i know how to... (1 Reply)
Discussion started by: Syth
1 Replies
6. UNIX for Dummies Questions & Answers
Hi,
I need execute a script every 30 minutes. As might be done without using cron
Thx. (6 Replies)
Discussion started by: pepeli30
6 Replies
7. Solaris
hi,
i am creating a daemon process for updating the file at regular interval.one problem with this is if anybody kills the daemon it wont update the file.anybody have idea how to rerun the daemon if it killed.the code is written in c++ in solaries environment.
thnaks & regards
suresh (8 Replies)
Discussion started by: suresh_rtp
8 Replies
8. UNIX for Dummies Questions & Answers
Dear all,
I am writing a shell that check the java application already run. If it is not run before it will run next commands.
ps -ef | grep java
Thank you :) (3 Replies)
Discussion started by: mr_bold
3 Replies
9. Programming
here's the problem, i have two processes that i need to run and both process should be run at a total of 1 minute each. how do i do that? and one more here's what the processes do: the 1st process show the '+" sign infinitely while the 2nd process displays the "-" infinitely. how could i count the... (1 Reply)
Discussion started by: kelogs1347
1 Replies
10. UNIX for Dummies Questions & Answers
I have a script that needs to run under ID say "xyz". the way I do normally is to "su" to the id, enter the password of "xyz" and run the process. However, is there any way run the process under "xyz" without "su" to the ID. A person with root access would be able to run any process under any ID as... (4 Replies)
Discussion started by: ucbus
4 Replies
SPEEDY(1p) SPEEDY(1p)
NAME
speedy - a persistent Perl interpreter
SYNOPSIS
speedy [ <perl options> ] [ -- <speedy options> ] [ <filename> ]
DESCRIPTION
speedy, short for SpeedyCGI, is a way to run perl scripts persistently, which can make them run much more quickly. The most common way to
make a script run persistently is by changing the interpreter line at the top of the script from:
#!/usr/bin/perl
to
#!/usr/bin/speedy
After the script is initially run, instead of exiting, the perl interpreter is kept running. During subsequent runs, this interpreter is
used to handle new executions instead of starting a new perl interpreter each time. A very fast frontend program, written in C, is exe-
cuted for each request. This fast frontend then contacts the persistent Perl process, which is usually already running, to do the work and
return the results.
Each perl script runs in its own Unix process, so one perl script can't interfere with another. Command line options can also be used to
deal with programs that have memory leaks or other problems that might keep them from otherwise running persistently.
Although SpeedyCGI is especially useful for CGI scripts, it can be used to keep any perl script running persistently. See CGI::Speedy-
CGI(3.pm) for a complete description of SpeedyCGI, including further details on CGI execution and Apache issues. This manual page is based
on that, but concentrates on running speedy from the command line.
OPTIONS
The speedy command line is the same as for regular perl, with the exception that SpeedyCGI specific options can be passed in after a "--".
For example the line:
#!/usr/bin/speedy -w -- -t300
at the top of your script will set the perl option `-w' and will pass the `-t' option to SpeedyCGI, setting the Timeout value to 300 sec-
onds.
The options can also be set at run-time from the perl script using the CGI::SpeedyCGI module.
OPTIONS AVAILABLE
See CGI::SpeedyCGI(3.pm) for a complete description of the options.
-p<string>
BackendProg : Path to the speedy backend program. (Default: /usr/bin/speedy_backend)
-B<number>
BufsizGet : Use <number> bytes as the maximum size for the buffer that receives data from the perl backend. (Default: 131072)
-b<number>
BufsizPost : Use <number> bytes as the maximum size for the buffer that sends data to the perl backend. (Default: 131072)
-g<string>
Group : Allow a single perl interpreter to run multiple scripts. See CGI::SpeedyCGI(3.pm) for details. (Default: `none')
-M<number>
MaxBackends : If non-zero, limits the number of speedy backends running for this perl script to <number>. (Default: 0)
-r<number>
MaxRuns : Once the perl interpreter has run <number> times, re-exec the backend process. Zero indicates no maximum. This option is
useful for processes that tend to consume resources over time. (Default: 500)
-t<number>
Timeout : If no new requests have been received after <number> seconds, exit the persistent perl interpreter. Zero indicates no
timeout. (Default: 3600)
-T<string>
TmpBase : Use the given prefix for creating temporary files. This must be a filename prefix, not a directory name. (Default:
`/tmp/speedy')
-v Version : Print the SpeedyCGI version and exit.
ENVIRONMENT
Environment variables can also be used to pass in options. This can only be done before the initial execution, not from within the script
itself. The name of the environment variable is always SPEEDY_ followed by the option name in upper-case. For example to set the speedy
Timeout option, use the environment variable named SPEEDY_TIMEOUT.
FILES
/tmp/speedy* A unix socket used to connect to the backend process. See speedy_backend(1) for more information.
AUTHOR
Sam Horrocks
http://daemoninc.com
sam@daemoninc.com
NOTES
This manual page was created by Niko Tyni <ntyni@iki.fi> for Debian GNU/Linux, because the original program does not have one. It is based
on the original and more complete CGI::SpeedyCGI(3pm) manual page.
BUGS
There are command-line parsing incompatibilities with the real Perl. These aren't very easy to fix, as even the perlrun manpage isn't
quite accurate on which parameters can be separated (like '-I') and which can't (like '-C'). speedy doesn't allow any of them to be sepa-
rated. It considers the first option without a leading dash as the script filename.
SEE ALSO
perl(1), CGI::SpeedyCGI(3pm), speedy_backend(1)
SPEEDY(1p)