05-02-2012
thanks for your help,
I checked shadow file and user (root) is not locked...
what else can be?
10 More Discussions You Might Find Interesting
1. 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
2. UNIX for Advanced & Expert Users
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
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
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
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
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
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
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
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
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
CHAGE(1) General Commands Manual CHAGE(1)
NAME
chage - change user password expiry information
SYNOPSIS
chage [-m mindays] [-M maxdays] [-d lastday] [-I inactive]
[-E expiredate] [-W warndays] user
chage -l user
DESCRIPTION
chage changes the number of days between password changes and the date of the last password change. This information is used by the system
to determine when a user must change her password. The chage command is restricted to the root user, except for the -l option, which may
be used by an unprivileged user to determine when her password or account is due to expire.
With the -m option, the value of mindays is the minimum number of days between password changes. A value of zero for this field indicates
that the user may change her password at any time.
With the -M option, the value of maxdays is the maximum number of days during which a password is valid. When maxdays plus lastday is less
than the current day, the user will be required to change her password before being able to use her account. This occurance can be planned
for in advance by use of the -W option, which provides the user with advance warning.
With the -d option, the value of lastday is the number of days since January 1st, 1970 when the password was last changed. The date may
also be expressed in the format YYYY-MM-DD (or the format more commonly used in your area).
The -E option is used to set a date on which the user's account will no longer be accessible. The expiredate option is the number of days
since January 1, 1970 on which the accounted is locked. The date may also be expressed in the format YYYY-MM-DD (or the format more com-
monly used in your area). A user whose account is locked must contact the system administrator before being able to use the system again.
The -I option is used to set the number of days of inactivity after a password has expired before the account is locked. The inactive
option is the number of days of inactivity. A value of 0 disables this feature. A user whose account is locked must contact the system
administrator before being able to use the system again.
The -W option is used to set the number of days of warning before a password change is required. The warndays option is the number of days
prior to the password expiring that a user will be warned her password is about to expire.
If none of the options are selected, chage operates in an interactive fashion, prompting the user with the current values for all of the
fields. Enter the new value to change the field, or leave the line blank to use the current value. The current value is displayed between
a pair of [ ] marks.
NOTE
The chage program requires shadow password file to be available. Its functionality is not available when passwords are stored in the
passwd file.
FILES
/etc/passwd - user account information
/etc/shadow - shadow user account information
SEE ALSO
passwd(5), shadow(5)
AUTHOR
Julianne Frances Haugh <jockgrrl@ix.netcom.com>
CHAGE(1)