11-25-2010
Inittab is not really designed for non system applications. It also lacks most SMF features which is the way to go for Solaris 10 and newer.
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
:confused:
I have a process which was schedule to run from 8am - 6pm daily. The scripts will search & run the commands that i was predefined in the database. Ususally, there were about 6-7 jobs for each submission and each job takes about 1-2 hrs and running one by one. And, I have a cron job... (3 Replies)
Discussion started by: hk_newbie
3 Replies
2. UNIX for Dummies Questions & Answers
Hi,
I'm very new to Unix so please bear with me... :)
Here is my requirement:
I need to create a cron job to run two different scripts at 1 a.m. every day.
Here's what I did:
I used the "crontab -e" command and created a crontab file using the vi editor.
When I exit the editor using... (3 Replies)
Discussion started by: yogiB
3 Replies
3. UNIX for Dummies Questions & Answers
Hi Everybody
I have small requirement that needs to be implemented in shell script.
Currently i have shell script which invokes a java process say "Process A" which runs in background.
If some one tries to invoke again the same shell script , then there should be some mechanism inside the... (23 Replies)
Discussion started by: appleforme1415
23 Replies
4. Shell Programming and Scripting
Hi guys,
I neet to run sqlldr to charge about 50,000 files every day to my DWH, so I need to make an script to keep about 100 processes of sqlldr running at the same time.
So, the issue is that i've been trying for a few days to make an script which can keep that amount of processes running, so... (2 Replies)
Discussion started by: razziel
2 Replies
5. Shell Programming and Scripting
Bonjour,
I have a large script with a lot of print statements and misc commands. Standard and error outputs are redirected like into the following code :
#!/usr/bin/ksh
LOG=/<some dir>/log
> $LOG
exec >>${LOG} 2>>${LOG}
print aaaaa
print bbbbb
print ccccc
...
some_cmd
That way,... (5 Replies)
Discussion started by: Fundix
5 Replies
6. Tips and Tutorials
For the newbies, I should have posted this years ago....
Here is the standard (tiny) "bread and butter" perl script (on Linux) I use in my crontab files to insure key processes are alive ( just in case ! ) like httpd, named, sshd, etc.
The example below if for named......
... (1 Reply)
Discussion started by: Neo
1 Replies
7. What is on Your Mind?
Odd thing.
I posted in the Solaris forum, new user, just asking for a bit of advice. Nothing too complicated. As of this post there have been 140 views and zero replies. So that got me thinking, is this normal? I had a look around, and I see the same thing on many other threads, and in other... (2 Replies)
Discussion started by: _JonB_
2 Replies
8. Programming
Hi
I'm adding http 1.1 GET to my project and trying to use “Keep-Alive” HTTP connections to the host, The problem is when I recv() the first page, it succeeds. However, the 2nd consecutive recv() will receive zero bytes, for which I really have no idea. As per HTTP 1.1 I have Connection: ... (6 Replies)
Discussion started by: Projecteer
6 Replies
LEARN ABOUT DEBIAN
speedy_backend
SPEEDY_BACKEND(1p) SPEEDY_BACKEND(1p)
NAME
speedy_backend - the backend process for a persistent Perl interpreter
SYNOPSIS
none ; this program is not meant to be called directly.
DESCRIPTION
speedy, short for SpeedyCGI, is a way to run perl scripts persistently, which can make them run much more quickly.
After the script is initially run, instead of exiting, the perl interpreter is kept running inside a backend process, speedy_backend. Dur-
ing subsequent runs, this interpreter is used to handle new executions instead of starting a new perl interpreter each time. A very fast
frontend program, speedy, written in C, is executed 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.
The speedy front end connects to the back end process, speedy_backend, via a Unix socket in /tmp. A queue is kept in a shared file in /tmp
that holds an entry for each process. In that queue are the pids of the perl processes waiting for connections. The frontend pulls a
process out of this queue, connects to its socket, sends over the environment and argv, and then uses this socket for stdin/stdout to the
perl process.
FILES
/tmp/speedy* A unix socket used to connect to the frontend process.
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.
SEE ALSO
perl(1), CGI::SpeedyCGI(3pm), speedy(1)
SPEEDY_BACKEND(1p)