I would like to start up multiple instances of syslog daemon. I am having a little difficulty. Is this at all possible?
I have separate syslog.conf1.... syslog.conf5 files.
I have linked the daemon to separate files syslogd1 ... syslogd5
I have arranged the rcd.2 start/stop scripts for... (9 Replies)
I am capturing text based reports with a specific program, which works no problem. However, since I send report warehouse output as they are migrated from the database software, on occasion when two capture process' initiate simultaneously, the capture file locks up. Is there a way to setup (in... (1 Reply)
Hi Gurus
I have a requirement like this. i use solaris OS..
if there are 2 instances of the same ksh file running in the directory, i need to kill the ksh file that started to run latest.
suppose ragha.ksh starts running thru cron in abc/xyz directory
now ragha.ksh started running by any... (3 Replies)
Hi,
I know that the answer to this is very simple, since I saw somebody do it some time back..but I forgot how.
The problem is, I have multiple instances of the same program running simultaneously and I want to kill them all in a single command.
I know that it can be done using awk '{print... (12 Replies)
Hi
I have a scenario where i need to check multiple instances of a running shell script (abc.sh) .
How can I find from inside a running shell script whether any other instance of the same script is running or not? If any other instance of same shell script is running I need to exit from... (4 Replies)
Hi,
This is my text file I'm trying to Grep.
Apple Location Greenland Rdsds dsds fdfd ddsads http Received Return Immediately Received End
My Grep command:
grep only--matching 'Location.*Received'
e.
Because the keyword Received appears twice, the Grep command will stop at the last... (0 Replies)
Hi,
This is my text file I'm trying to Grep.
Apple Location Greenland Rdsds dsds fdfd ddsads http Received Return Immediately Received End
My Grep command:
grep only--matching 'Location.*Received'
Because the keyword Received appears twice, the Grep command will stop at the last... (3 Replies)
Hello. This shouldn't be an unusual problem, but I cannot find anything about it at google or at other search machine.
So, I've made an application using C++ and QtCreator. I 've made a new mime type for application's project files.
My system (ubuntu 10.10), when I right click a file and I... (3 Replies)
Suppose I declare
pthread_t clear_thread;
and then
pthread_create(&clear_thread, &detach, clear_message, this);
the thread is supposed to go away, perform the service it is intended to procide, and then kill itself.
A little while later, I require this service again, so I say
... (2 Replies)
Discussion started by: clerew
2 Replies
LEARN ABOUT OSF1
queuedefs
queuedefs(4) Kernel Interfaces Manual queuedefs(4)NAME
queuedefs - Queue description file for at, batch, and cron commands
DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron or specifies other characteristics for cron. Each noncom-
ment line in this file describes either one queue or a cron characteristic. Each uncommented line should be in one of the following for-
mats.
q.[njobj][nicen][nwaitw] max_jobs=mjobs log=lcode
The fields in these lines are as follows: The name of the queue. Defined queues are as follows: The default queue for jobs started by at
The default queue for jobs started by batch The default queue for jobs run from a crontab file
Queues d to z are also available for local use. The maximum number of jobs that can be run simultaneously in the queue; if more
than njob jobs are ready to run, only the first njob jobs will be run. The others will be initiated as currently running jobs ter-
minate. The nice(1) value to give to all jobs in the queue that are not run with a user ID of superuser. The number of seconds to
wait before rescheduling a job that was deferred because more than njob jobs were running in that queue, or because the system-wide
limit of jobs executing (max_jobs) has been reached. The maximum number of active jobs from all queues that may run at any one
time. The default is 25 jobs. Logging level of messages sent to a log file. The default is 4. Defined levels are as follows:
level-code level
0 None
1 Low
2 Medium
3 High
4 Full
Lines beginning with # are comments, and are ignored.
EXAMPLES
The following file specifies that the b queue, for batch jobs, can have up to 50 jobs running simultaneously; that those jobs will be run
with a nice value of 20. If a job cannot be run because too many other jobs are running, cron will wait 60 seconds before trying again to
run it. All other queues can have up to 100 jobs running simultaneously; they will be run with a nice value of 2. If a job cannot be run
because too many other jobs are running cron will wait 60 seconds before trying again to run it. b.50j20n60w
The following file specifies that a total of 25 active jobs will be allowed by cron over all the queues at any one time, and cron will log
all messages to the log file. The last two lines are comments that are ignored. max_jobs=25 log=4 # This is a comment # And so is this
FILES
Main cron directory The default location for the queue description file.
RELATED INFORMATION
Commands: at(1), cron(8), crontab(1), nice(1)
delim off
queuedefs(4)