10-25-2011
This error in cron log will come when a user ID is having password policy set on it and it tries to execute a scheduled script.
I have seen this in solaris 8.
I think you have collected a wrong output since the bad user comment is logged at 11 hrs whereas the adm 6739 job is at 10 hrs.
Regards,
Vishal
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
Here im using WinSCP and looking into the remote dir var/adm/cron and I get the following error.Is this bcoz i dont have admin privileges:
Cannot get real path for '/var/adm/cron'.
Unexpected OK response.
Error code: 0
Error message from server: Success
Request code: 16
BTW im... (1 Reply)
Discussion started by: thumsup9
1 Replies
2. Solaris
hi experts,
i'm having more error log on /var/adm/messages could anyone help to description what is this error logs means???? and how to fix it? below is the logs :
Nov 22 20:03:40 USSDGtbs-1 unix:
Nov 22 20:03:40 USSDGtbs-1 ^Mpanic/thread=3001345edc0:
Nov 22 20:03:40 USSDGtbs-1 unix: ... (2 Replies)
Discussion started by: bucci
2 Replies
3. AIX
Hi,
I can use 'crontabs –e' and do all the scheduling I like. However I would like to auto send myself just the cronjobs logs that fail. That is to say the PIDs that fail and the related lines with those PID’s only. (Not the full set of logs) Has anyone done this work? Or does an AIX 5.3 tool... (0 Replies)
Discussion started by: Keith Johnson
0 Replies
4. Shell Programming and Scripting
Hi
A Ksh script is deployed in a server and executed through cronjob.
If one of the line in the middle of the script fails . Are the remaining lines executed ? (3 Replies)
Discussion started by: Sivaswami
3 Replies
5. Solaris
Hello All,
Anybody please help me to know ,what happens when a user having entry in both cron.allow and cron.deny files.Wheather the user will be able to access the crontab???
Thanks in advance
Vaisakh (5 Replies)
Discussion started by: ksvaisakh
5 Replies
6. UNIX for Dummies Questions & Answers
Warning... I am a newb. :)
I basically know how to add/rm users, kill pids and monitor diskspace. Not an idiot, but honestly a windows database person. I don't know much about what I am asking about.
In the /var/adm/messages file, today this was added:
Jan 24 09:16:51 my_server login: ... (3 Replies)
Discussion started by: madEG
3 Replies
7. Solaris
I am getting the following error in the cron log:
! bad user (root) Wed Sep 22 14:30:00 2010
< root 8989 c Wed Sep 22 14:30:00 2010 rc=1
What does this mean? (5 Replies)
Discussion started by: jastanle84
5 Replies
8. Shell Programming and Scripting
Suppose user 'asdf' is not logged into server 'bbbb', but the server is up. User 'asdf' has cron job. Will it be executed? (1 Reply)
Discussion started by: thulasidharan2k
1 Replies
9. Solaris
Hi everyone,
I got error which is "!bad user (root)" in crontab...
I tried changing password,
I checked etc/cron/cron.allow and cron.deny,
And also I checked the permissions of my files,
its(my crontab script) still not working....
Please help... (12 Replies)
Discussion started by: ijustneeda
12 Replies
10. Shell Programming and Scripting
I've created a pretty straightforward shell script to do backups via rsync. Every night it rsyncs a copy of a website (approx 60GB) to the local machine. Once a week, after the rsync step, it zips the local copy of the whole site into 2GB chunks and places them in another folder.
When running... (3 Replies)
Discussion started by: Agreppa
3 Replies
log(8) System Manager's Manual log(8)
NAME
log - Records input and output from a program
SYNOPSIS
/usr/sbin/log <logfile> <command>
OPERANDS
The file in which to record the interaction being logged. The command to execute.
DESCRIPTION
The log program runs <command> and logs the input to and output from <command> to the <logfile> file. Input and output are logged until
<command> exits, the log program exits, and the exit status of <command> is returned.
The log program is used by the system installation procedure and the it(8) command to create the /var/adm/smlogs/install.log and
/var/adm/smlogs/it.log installation log files.
RESTRICTIONS
Because the log program is used in the installation standalone environment, program size was the greatest concern in its implementation.
The log program does not search for the PATH variable to locate <command> and error messages are terse.
The log program causes <command> to take standard input from and write standard output and standard error to UNIX pipes. Some commands
will not be able to operate in this environment; therefore, it is suggested that you use the script(1) command instead. UNIX shells will
not issue prompts when run from log unless the shell is started with an explicit interactive switch (-i for most shells). For example, log
foo.tmp /sbin/sh -i
In the previous example, foo.tmp is the name of <logfile>.
The log program intercepts end-of-file (usually Ctrl/d). Therefore programs which normally receive end-of-file as an exit command must
exit by some other means.
ERRORS
Log open error
Explanation:
The log program was unable to open <logfile>. Verify that the directory exists and that ownerships and permissions are set correctly.
Exec Error
Explanation:
The log program was unable to execute <command>. Verify that you specified a full pathname for <command> and that <command> is an exe-
cutable file.
Fork Error
Explanation:
The log program was unable to create one of the processes it requires to log data.
SEE ALSO
Commands: it(8), script(1)
log(8)