03-12-2019
Please post your exact crontab file entries for these two users:
We need to see the exact crontab file entry to give you the help you are asking for.
Thanks.
10 More Discussions You Might Find Interesting
1. Programming
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)
Discussion started by: handak9
2 Replies
2. Shell Programming and Scripting
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)
Discussion started by: reader_regular
0 Replies
3. UNIX for Advanced & Expert Users
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)
Discussion started by: prkfriryce
2 Replies
4. UNIX for Dummies Questions & Answers
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)
Discussion started by: jithinravi
5 Replies
5. UNIX for Advanced & Expert Users
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)
Discussion started by: capibolso
1 Replies
6. Cybersecurity
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)
Discussion started by: KennyCason
0 Replies
7. UNIX for Dummies Questions & Answers
hi power went out. next day unix sco wont boot up error code 303. any help appreciated as we are clueless. (11 Replies)
Discussion started by: fredthayer
11 Replies
8. Linux
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)
Discussion started by: psoheil
1 Replies
9. UNIX for Advanced & Expert Users
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)
Discussion started by: SULTAN01
1 Replies
10. Linux
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 FREEBSD
crontab
CRONTAB(1) BSD General Commands Manual CRONTAB(1)
NAME
crontab -- maintain crontab files for individual users (V3)
SYNOPSIS
crontab [-u user] file
crontab [-u user] { -l | -r | -e }
DESCRIPTION
The crontab utility is the program used to install, deinstall or list the tables used to drive the cron(8) daemon in Vixie Cron. Each user
can have their own crontab, and though these are files in /var, they are not intended to be edited directly.
If the allow file exists, then you must be listed therein in order to be allowed to use this command. If the allow file does not exist but
the deny file does exist, then you must not be listed in the deny file in order to use this command. If neither of these files exists, then
depending on site-dependent configuration parameters, only the super user will be allowed to use this command, or all users will be able to
use this command. The format of these files is one username per line, with no leading or trailing whitespace. Lines of other formats will
be ignored, and so can be used for comments.
The first form of this command is used to install a new crontab from some named file or standard input if the pseudo-filename '-' is given.
The following options are available:
-u Specify the name of the user whose crontab is to be tweaked. If this option is not given, crontab examines ``your'' crontab, i.e.,
the crontab of the person executing the command. Note that su(1) can confuse crontab and that if you are running inside of su(1) you
should always use the -u option for safety's sake.
-l Display the current crontab on standard output.
-r Remove the current crontab.
-e Edit the current crontab using the editor specified by the VISUAL or EDITOR environment variables. The specified editor must edit
the file in place; any editor that unlinks the file and recreates it cannot be used. After you exit from the editor, the modified
crontab will be installed automatically.
FILES
/var/cron/allow List of users allowed to use crontab
/var/cron/deny List of users prohibited from using crontab
/var/cron/tabs Directory for personal crontab files
DIAGNOSTICS
A fairly informative usage message appears if you run it with a bad command line.
SEE ALSO
crontab(5), cron(8)
STANDARDS
The crontab command conforms to IEEE Std 1003.2 (``POSIX.2'') with the exception that the dangerous variant of calling crontab without a file
name in the first form of the command is not allowed by this implementation. The pseudo-filename '-' must be specified to read from standard
input. The new command syntax differs from previous versions of Vixie Cron, as well as from the classic SVR3 syntax.
AUTHORS
Paul Vixie <paul@vix.com>
BSD
May 13, 2010 BSD