09-23-2010
I have 2 quick suggestions:
First, Was the cron daemon running? Do a ps -ef|grep. Of course if it is running now, maybe it wasn't running then.
Second, I've never seen that error, but I noticed the "rc=1". Was the system in single user mode? Just wondered.
9 More Discussions You Might Find Interesting
1. HP-UX
Hello All,
I work as a system admin at a company of about 600 users on a HP-UX server. We have an IT department of about 15. My problem is that we give out the root password to the majority of them, they are phone support techs, as they need to get in to kill processes and setup users and... (4 Replies)
Discussion started by: Setan
4 Replies
2. Solaris
I'm running sendmail (8.13.8+Sun/8.13.8/Submit) solaris 10.
When I send mail to root at the command line (whether I use a full-qualified address or just root), I get the error message
root... User address required.
Sending mail to root (either at the command line or in a cron job),... (10 Replies)
Discussion started by: csgonan
10 Replies
3. UNIX for Dummies Questions & Answers
Does anyone know if this is possible?
I want to give some users access to root's crontab but only with a read privilege.
Is this possible to do or can only root or people with full root sudo view root's cron? (4 Replies)
Discussion started by: LordJezoX
4 Replies
4. Shell Programming and Scripting
Hallo,
i need a Prompting read in my script:
read -p "Enter your command: " command
But i always get this Error:
-p: is not an identifier
When I run these in c-shell i get this error
/usr/bin/read: read: bad option(s)
How can I use a Prompt in the read command? (9 Replies)
Discussion started by: wiseguy
9 Replies
5. Red Hat
I am trying to install openmotif22-2.2.3-18.src.rpm,
after I typed in " rpm -i openmotif22-2.2.3-18.src.rpm"
the following message comes out:
warning: user owen does not exist - using root
warning: group owen does not exist - using root
I am install openmotif under root account.
Do... (2 Replies)
Discussion started by: fishwater00
2 Replies
6. Red Hat
Hi,
I am seeing the following errors in my environment, not sure why is it happening, any ideas? Thanks.
kernel: RPC: bad TCP reclen 0x73746174 (non-terminal ) Dec 17 02:14:48 kernel: RPC: bad TCP reclen 0x63480000 (large) Dec 17 02:14:48
kernel: RPC: bad TCP reclen 0x633f0000 (large) Dec... (5 Replies)
Discussion started by: amarlinux
5 Replies
7. AIX
Our AIX servers send e-mails which have the "from" address set to "root@company.com" for our root user ("C{M}company.com" in /etc/sendmail.cf). The problem is that when bad e-mails are sent out or rejected by remote servers, they are being returned and delivered to e-mail box of "Mary Root".
... (2 Replies)
Discussion started by: kah00na
2 Replies
8. Shell Programming and Scripting
Close duplicate thread. (0 Replies)
Discussion started by: denissi
0 Replies
9. UNIX for Beginners Questions & Answers
I am looking t run root level command on multiple servers, but all servers have only "su - " permission available in sudoers.
please help me if any way that I can run command using help of "su -"
My script
for hosts in `cat hosts.txt`;
do
echo "###########################Server Name-... (5 Replies)
Discussion started by: yash_message
5 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)