Sponsored Content
Full Discussion: Bad user root in crontab
Operating Systems Solaris Bad user root in crontab Post 302633695 by ijustneeda on Wednesday 2nd of May 2012 10:36:03 AM
Old 05-02-2012
still not working....
there is no warn for pass in shadow file.

Thanks anyway... but i ll be waiting for other advises...
I have been trying to solve this problem from like 5 days...
I guess there is a solaris/cron expert in somewhere here... Smilie
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Possible to give non root user sudo to "crontab -l"

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

2. UNIX for Advanced & Expert Users

crontab : bad minute error

when i say $crontab z it says ==> "z":6: bad minute "z":6: bad minute errors in crontab file, can't install. any clue why its happening? (1 Reply)
Discussion started by: crackthehit007
1 Replies

3. AIX

Crontab cannot run by non-root user

Good morning everybody. I have just receiedv a complaint from our DBA saying that if he create a scripts to run some Oracle performance scripts using crontab and the scheduling part is ok but the job is failed when I checked on /var/adm/cron/log. I have tried his scripts using Oracle id directly... (4 Replies)
Discussion started by: kwliew999
4 Replies

4. UNIX for Dummies Questions & Answers

If user has own crontab, results in accumulation of root CRON processes

Hello, I seem to be having a problem with accumulation of root CRON jobs occuring when I have a user's cron job(s) running. Here is an example of a user's crontab file: */1 * * * * echo "hello" > /dev/nullps aux|grep CRON root 14333 0.0 0.0 91236 2172 ? S ... (12 Replies)
Discussion started by: Narnie
12 Replies

5. UNIX for Dummies Questions & Answers

Cannot run crontab :1: bad minute error

Hi can any one help me out. while running crontab , m getting error bad minute time.. how to resolve this error. i created 1 txt file a.cron mirrordir -vm \home\t \homet1 & i saved it. then i created a crontab file ..with crontab -e & i added a line in it. * 1 * * * \root\a.cron & i save... (2 Replies)
Discussion started by: unxdost114
2 Replies

6. Solaris

"! bad user (root)" in cron log

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

7. UNIX for Dummies Questions & Answers

Editing crontab of non-root user from file

Hi All, Ref: "build crontab from a text file" in same forum. (I am not allowed to post URL's in the first post) We are reorganizing our UNIX Crontab file by first making changes in a word pad text file. The intent is to then copy it back to Crontab. Will this work? Copy and Paste does not... (6 Replies)
Discussion started by: nivedhitha
6 Replies

8. Hardware

What are the possible action regarding having bad sector in my ext4 root partition?

Hi, I would like to ask about actions taken if any regarding having a few bad sector (67 bad sector according to DISK UTILITY) on my root ext partition except from buying a new HD and cloning it since my laptop is a 1 year old. Question: About clonzilla before this bad sector happens i used... (5 Replies)
Discussion started by: jao_madn
5 Replies

9. UNIX for Dummies Questions & Answers

Sudo to delegate permission from non-root user to another non-root user

I've been through many threads before i decide to create a separate thread. I can't really find the solution to my (simple) problem. Here's what I'm trying to achieve: As "canar" user I want to run a command, let's say "/opt/ocaml/bin/ocaml" as "duck" user. The only to achieve this is to... (1 Reply)
Discussion started by: canar
1 Replies

10. Shell Programming and Scripting

Crontab error - bad hour

Hi All, While setting the crontab i am getting the below error, "/tmp/crontab.XXXXwKymEc" 156L, 15621C written crontab: installing new crontab "/tmp/crontab.XXXXwKymEc":74: bad hour Please help. Thanks (2 Replies)
Discussion started by: nag_sathi
2 Replies
shadow(4)						     Kernel Interfaces Manual							 shadow(4)

NAME
shadow - shadow password file SYNOPSIS
DESCRIPTION
The file is created from the file by the command. It is readable only by a privileged user. It can be modified by the and commands. Pro- grams may use the interfaces described in the getspent(3C) manpage to access this information. These functions return a pointer to an structure, which is defined in the header file. Fields The file is an ASCII file consisting of any number of user entries separated by newlines. Each user entry line consists of the following fields separated by colons: login name Each login name must match a login name in puts the user entries in in the same order as the entries. encrypted password The password field of each entry contains an "x", and the actual encrypted passwords reside in The encrypted password field consists of 13 characters chosen from a 64-character set of "digits". The characters used to represent "digits" are for 0, for 1, through for 2 through 11, through for 12 through 37, and through for 38 through 63. If the SHA11i3 product is installed, the password field may contain the prefix , where n is a label identifying an alterna- tive algorithm used for the password hash. Using the new algorithm results in an encrypted password field which is longer than 13 characters. The password field will consist of digits from the same 64-character set, as well as the additional character used as a delimiter. If this field is null, then there is no password and no password is demanded on login. Login can be prevented by entering a character that is not a part of the set of digits (such as *). last change The number of days since January 1, 1970 that the password was last modified. min days The minimum period in days that must expire before the password can be changed. See also in security(4) and the command in passwd(1). max days The maximum number of days for which a password is valid. A user who attempts to login after his password has expired is forced to supply a new one. If min days and max days are both zero, the user is forced to change his password the next time he logs in. If min days is greater than max days, then the password cannot be changed. These restrictions do not apply to the superuser. See also in security(4) and the command in passwd(1). warn days The number of days the user is warned before his password expires. See also in security(4) and the command in passwd(1). inactivity The maximum number of days of inactivity allowed. This field is set with the option of either the or command. If this value is greater than zero, then the account is locked if there have been no logins to the account for at least the specified num- ber of days. If this value is less than or equal to zero, the value is determined by the attribute. See the description of in security(4). expiration The absolute number of days since Jan 1, 1970 after which the account is no longer valid. A value of zero in this field indicates that the account is locked. reserved The reserved field is always zero and is reserved for future use. Notes The file is not applicable to a system which has been converted to a trusted system. WARNINGS
HP-UX 11i Version 3 is the last release to support trusted systems functionality. FILES
system password file shadow password file SEE ALSO
login(1), passwd(1), pwconv(1M), pwunconv(1M), useradd(1M), userdel(1M), usermod(1M), crypt(3C), getspent(3C), putspent(3C), nss- witch.conf(4), passwd(4), security(4). shadow(4)
All times are GMT -4. The time now is 08:17 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy