Hi,
I am trying to write stuff to a shared memory using a writer, and reading the corresponding stuff using a reader. I am facing problems while releasing the lock, as a result of which I am having segmentation faults. The code is as follows...
/********** writer.c ***********/
... (1 Reply)
I have been doing unix scripting for quite awhile and there seems to be a wealth of information on it.
Now I am working on migrating an intel based application to a new server.
I need to modify some existing scripts, but am having trouble finding information on windows scripting, a forum similar... (2 Replies)
I have a volume managed by Veritas Storage Migrator 6.0 running on Solaris 10. It has one managed volume and one tape robot it shares with netpackup (separate volume pools). When I check the process tree I am not seeing any migration processes running, but when I check the panel on the tape robot... (0 Replies)
Hi, I have created an autosys job which calls an exe and updates its output files. The job is failing without updating the output and error files.
I if restart the usvmapgrnd01.pc.ml.com machine, the job runs successful for first time and fails rest of the time. Please let me know what might be... (0 Replies)
I am attempting to write a program with multiple POSIX threads. I want to ensure all threads are released at the same time. I am (trying to) use a semaphore to accomplish this.
Without too much irrelevant information, I declare my semaphore with 0 of 25 resources available. Is there a way... (7 Replies)
Hi Guys !
I have found this problem many times that the swap space (/tmp space more precisely )of my Server becomes full specially when i run a complete back up of the server .
once the /tmp space is full I am not able to run simple commands as i get error like :
fork no space
on... (6 Replies)
Hi Guys !
I have found this problem many times that the swap space (/tmp space more precisely )of my Server becomes full specially when i run a complete back up of the server .
once the /tmp space is full I am not able to run simple commands as i get error like :
fork no space
on... (4 Replies)
Hey Guys,
I need a help,
After I upgraded my server to AIX 6.1.4 the port 80 is occupied by a Java process
bash-3.00# netstat -Aan | grep "*.80"
f1000700007d7bb0 tcp 0 0 *.80 *.* LISTEN
bash-3.00# rmsock f1000700007d7bb0 tcp
usage: rmsock Addr... (2 Replies)
Hi everyone,
i have a question about the Memory Management in AIX 6.1.
I have
- 128 GB RAM and
- 70 GB Page Space.
The application i am running on this machine is doing some operations in perl. These are done only once a day and uses both memory and paging space. My problem... (1 Reply)
I had a simple automation process to take config backup from san switches to windows via SSH. This can be accomplished using plink.
My script was working fine earlier but from last few days it is not collecting data and the error which i am getting is below.
"":confused:
I have done the... (6 Replies)
Discussion started by: nirjhar17
6 Replies
LEARN ABOUT HPUX
queuedefs
queuedefs(4) Kernel Interfaces Manual queuedefs(4)NAME
queuedefs - queue description file for at, batch, and crontab
SYNOPSIS DESCRIPTION
The file describes the characteristics of the queues managed by (see cron(1M)). Each non-comment line in this file describes one queue.
The format of the lines are as follows:
[njob[nice[nwait
The fields in this line are:
q The name of the queue, such that is the default queue for jobs started by (see at(1)), is the queue for jobs started by
(see at(1)), and is the queue for jobs run from a file (see crontab(1)). Queue names through designate user-defined
queues.
njob The maximum number of jobs that can be run simultaneously in that queue. Although any number can be specified here, (see
cron(1M)) by default limits the number of jobs that can be run on all the queues to 100. This limitation can be removed
by setting the variable to 1 in the file.
nice The value to give to all jobs in that queue that are not run with a user ID of super-user (see nice(1)). The default
value is 2.
nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that
job's queue, or because more than 100 jobs were running in all the queues (see njob above).
EXAMPLES
Consider the following file:
The file is interpreted as follows:
The queue, for jobs (see at(1)), can have up to 4 jobs running simultaneously, and those jobs will be run with a value of
1.
Since no nwait value is given, if a job cannot be run because too many other jobs are running, will wait 60 seconds
before trying again to run it (see cron(1M)).
The queue, for jobs (see at(1)), can have up to 2 jobs running simultaneously. Those jobs will be run with a value of 2.
If a job cannot be run because too many other jobs are running, will wait 90 seconds before trying again to run it.
All other queues can have up to 100 jobs running simultaneously. They will be run with a value of 2, and if a job cannot be run because
too many other jobs are running, will wait 60 seconds before trying again to run it.
SEE ALSO at(1), nice(1), crontab(1), cron(1M), proto(4).
STANDARDS CONFORMANCE queuedefs(4)