06-20-2019
Are you considering to run your "status checking" script in cron?
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi guys,
I Have written a script,In that it will call another file which contains the sql quaries.
while wxecuting that I am getting the below exception
01/16|06:28:06:16800: Operating System Error|Failed to open output file
Can anybody help me about this,,Its urgent (0 Replies)
Discussion started by: Anji
0 Replies
2. Shell Programming and Scripting
Hello, i am familiar enough with unix to do some damage but thats about it.
We have a set of RS/6000 43P Model 150's running AIX for our Catia V4 programmers.
back in the 90's a script was written to automate the conversion of files into machine code. that script has started giving us... (0 Replies)
Discussion started by: jgruenwald
0 Replies
3. Shell Programming and Scripting
Hello All,
Can somebody help me with this script. I have an output file with a list of servers ips and ports. I need to be able to run this script to list all the server ips in the outfile and find out if the port is open or not.
#!/bin/sh
IFS=#;for i in $(cat portTest);
do
# check... (2 Replies)
Discussion started by: liketheshell
2 Replies
4. Solaris
Hi,
I am working with solaris 9 and I want to install perforce on that,so I downloaded the p4v.bin file and try to install it by the command
./p4v
after that it is giving the error---
ld.so.1: ./p4v.bin: fatal: libm.so.2: open failed: No such file or directory
Killed
I am not... (3 Replies)
Discussion started by: smartgupta
3 Replies
5. Solaris
Hi Friends
I have a compiler(Sun Forte,I believe) running in my Solaris 9 box.
since y'day my development team is finding this error when they compile:
ld.so.1: expr: fatal: libgmp.so.3: open failed: No such file or directory
I ran a search for this file and found it in one of my file... (2 Replies)
Discussion started by: Hari_Ganesh
2 Replies
6. UNIX for Dummies Questions & Answers
Hi,
I have try to ndm to one server to another server. but i am getting this error. what is this error? are files not in source folder?
Source file open failed. Error= 2
Regards,
Balamurgan (1 Reply)
Discussion started by: krbala1985
1 Replies
7. Red Hat
Hi,
# yum --skip-broken -y update
rpmdb: Thread/process 6657/3078387392 failed: Thread died in Berkeley DB library
error: db3 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Packages index using db3 - (-30974)
error: cannot open... (3 Replies)
Discussion started by: sef alislam
3 Replies
8. Shell Programming and Scripting
Hi All,
I have a requirment, i need to get the list of all the process which are running from last two days on my unix server and also to put this list into an another file.
i am giving you a sample example :
$ ps -ef
UID PID PPID C STIME TTY TIME CMD (1 Reply)
Discussion started by: akshu.agni
1 Replies
9. UNIX for Beginners Questions & Answers
I just updated my rdesktop to 1.8.3 from source ( on Slackware 11 ) and had troubles with arrow keys/page up/page down not working.
I see this on the console:
ERROR: Failed to open keymap en-us
The fix is a permission change. I initially looked at /usr/share/rdesktop/keymaps and everything... (1 Reply)
Discussion started by: agentrnge
1 Replies
10. Shell Programming and Scripting
Hi, The below commands works fine on serverB
. /etc/profile;
cd /export/home/user2/utils/plugin/
./runme.shHowever, when i run the same commands from serverA it fails
$ ssh -q user2@serverB ". /etc/profile; cd /export/home/user2/utils/plugin; ./runme.sh"Output Error:
Please find the below... (8 Replies)
Discussion started by: mohtashims
8 Replies
LEARN ABOUT XFREE86
queuedefs
queuedefs(4) File Formats queuedefs(4)
NAME
queuedefs - queue description file for at, batch, and cron
SYNOPSIS
/etc/cron.d/queuedefs
DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue.
The format of the lines are as follows:
q.[njobj][nicen][nwaitw]
The fields in this line are:
q The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs started by batch (see
at(1)); c is the default queue for jobs run from a crontab(1) file.
njob The maximum number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first
njob jobs will be run, and the others will be run as jobs that are currently running terminate. The default value is 100.
nice The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user. 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 the system-wide limit of jobs executing has been reached. The default value is 60.
Lines beginning with # are comments, and are ignored.
EXAMPLES
Example 1: A sample file.
#
#
a.4j1n
b.2j2n90w
This file specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value
of 1. As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying
again to run it.
The b queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2. If a job
cannot be run because too many other jobs are running, cron(1M) 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 nice value of 2, and if a job cannot be run because too many other jobs
are running cron will wait 60 seconds before trying again to run it.
FILES
/etc/cron.d/queuedefs queue description file for at, batch, and cron.
SEE ALSO
at(1), crontab(1), nice(1), cron(1M)
SunOS 5.10 1 Mar 1994 queuedefs(4)