Hi,
I am using gmake to compile a c program with a makefile. The make file runs ld. I get the following error
jsh1035c:/users/egate453/admegate/kapil/samples $ gmake -e -f GNUmakefile queue_c
gmake -f ./GNUmakefile queue_c in_objdir=1 build_root=/users/egate453/admegate/kapil/samples... (2 Replies)
Plz advise on the following error for a crontab job i have scheduled for running a script
/usr/lib/dld.sl: Can't open shared library: /home/build3p/PMReleases/Symphony711/HP-UX/rw/710/lib/libtls4d.sl
/usr/lib/dld.sl: No such file or directory
/ushhquest/data001/Scripts/Inform/Build_Data.sh:... (0 Replies)
I am using an ssh pub key on two remote servers to allow ssh session without authentication. Both servers have the same id_rsa.pub copied from the host into the remote servers ~user/.ssh/authorized_keys. There is no passphrase for this key either.
The problem is that I am able to ssh into one... (2 Replies)
am getting the following error while trying to create a new crontab file:
(jravisha) jravisha- crontab -e
no crontab for jravisha - using an empty one
crontab: installing new crontab
"/tmp/crontab.XXXXH3SJgR":1: premature EOF
errors in crontab file, can't install.
Do you want to retry the... (5 Replies)
My PAM module seems to work right but it fails in authentication. Althought it can't authenticate, the session module works and the software who uses it executes well.
For example, when I login through "gdm" using pam to authenticate against an ldap server
/var/log/auth.log shows
Any... (1 Reply)
Ssh connections using shared public keys issue “authentication failure” messages, then succeed with “session opened”.
I have found a few other threads with similar issue, but no solutions offered. :wall:
How can I eliminate the failure messages?
Environment:
$ uname -a Linux... (0 Replies)
Hello All,
I am having trouble connecting to a Fedora 16 Server using NX Client for Windows 7. It gives the following error:
NX> 203 NXSSH running with pid: 7124
NX> 285 Enabling check on switch command
NX> 285 Enabling skip of SSH config files
NX> 285 Setting the preferred NX options
NX>... (1 Reply)
I was bogged with an error “Authentication Failure” for all of my cron jobs in Linux Ubunutu.
root@Test:~# tail -f /var/log/syslog | grep cron
Dec 11 16:38:01 Test cron: Authentication failure
Dec 11 16:38:01 Test cron: Authentication failure
Dec 11 16:38:09 Test cron: (CRON) INFO (pidfile... (1 Reply)
Dear All,
I have Google Two Factor (2F) Authentication enabled for sshd on most of my Linux servers. This works well and I highly recommend it.
My question is:
Has anyone set this up for rsync which runs in a crontab?
For example, supposed we have this simple crontab script:
... (5 Replies)
Discussion started by: Neo
5 Replies
LEARN ABOUT POSIX
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)
03-12-2019
