08-01-2006
127 usually means (in scripts written by folks who know about 'special meanings' for exit codes) that a command was not found - it frequently releates to a PATH problem.
If the script tried to <exec command> a command it could not find in the PATH variable for example....
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I have created a shell script that spawns multiple background processes (spawns sqlplus application). I use an array to capture the process id of those background processes. I then loop through the array and issue a 'wait' command to wait on the process id that was captured in the array. I am... (2 Replies)
Discussion started by: max_largo
2 Replies
2. UNIX for Advanced & Expert Users
my apache 2.0 is up and running but after trying to reconfigure it for specifics I ended up with a permanent eror message that I can't seem to get rid of .. when I run the server ( just / */apachect1 start )
the message reads "cannot locate name localhost for server 127.0.0"
so far I have tried... (2 Replies)
Discussion started by: moxxx68
2 Replies
3. Solaris
I have just installed Solaris 10 X86 today, but I can't use internet at all on it.
When I was installing it, it only asked me to create a hostname, without even asking me this computer is "networked" or "non-networked".
After I finished installation, I use "netstat -rn" command, and only see... (3 Replies)
Discussion started by: Diamondust
3 Replies
4. HP-UX
HP-UX B.11.23 U 9000/800 636114222 unlimited-user license
I see this error in my logs sometimes and have very little info on it...
I have searched online for some documentation and haven't been able to find much on this issue.
The only thing I found on one site is that if my /tmp folder... (4 Replies)
Discussion started by: zixzix01
4 Replies
5. Shell Programming and Scripting
Hi All,
While running shell script i got following output.
interpreter "usr/bin/ksh" not found
sh: step1.sh: not found.
ldnhpux | oracle >echo $?
127
- Running command "which ksh" retruns "usr/bin/ksh".
- I found some information on web stating to remove extra carriage return chars,... (8 Replies)
Discussion started by: RuchirP
8 Replies
6. Solaris
one of our sparc servers is having this problem:
Jun 27 13:05:00 sparki sendmail: p5: from=root, size=309, class=0, nrcpts=1, msgid=<201106271305.p5@sparki>, relay=root@localhost
Jun 27 13:05:00 sparki sendmail: p5: to=root, ctladdr=root (0/0), delay=00:00:00, xdelay=00:00:00, mailer=relay,... (3 Replies)
Discussion started by: orange47
3 Replies
7. Solaris
I was checking routing table, and noticed that our server has a lot packets from localhost:
Routing Table: IPv4
Destination Gateway Flags Ref Use Interface
-------------------- -------------------- ----- ----- ------ ---------
..
127.0.0.1 127.0.0.1 ... (1 Reply)
Discussion started by: orange47
1 Replies
8. UNIX for Advanced & Expert Users
Hi All,
I am trying to create background processes and then check their status later. But I am getting return codes as 0,127 randomly
On checking the return codes for wait, I found the below. Do I need to treat return code of 127 as successful as well?? as we know the process id passed is... (7 Replies)
Discussion started by: tostay2003
7 Replies
9. IP Networking
Which one should I use in '/etc/hosts'?
Please explain in details.
Random quotes on the topic: (2 Replies)
Discussion started by: useretail
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)