02-22-2002
After you set them up, you could use the "chage" command to set their last password change back to the beginning of time... (1970-01-01). I suppose they'd have to have password expiry turned on first though... You could have their password expire in some ungodly amount of time that they'll never encounter, though.
I think I've only used linuxconf once, so I don't know if you can do it through there (I stopped using it because it broke stuff when you changed something manually, and in later linuxconf).
Hope someone else can come up with a better idea than that.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
yeah, I tried basically everything I can find from reading books and asking people but I haven't gotten it to work.
is there anything else that can be done. I mean, this internal modem I got is like the last thing I expected Linux not to find (2 Replies)
Discussion started by: TRUEST
2 Replies
2. UNIX for Advanced & Expert Users
Hi,
I notice in my Sun Solaris 8 sparc worstation, I am able to change my password to same existing password.
That is, right now my password is abc, and I change it with "passwd" command and change it abc again. It will accept.
How can I make it such that it will not accept same password?... (3 Replies)
Discussion started by: champion
3 Replies
3. Red Hat
All,
I have a RedHat 9 box which I need to figure out how to get it to stay in full duplex mode after a reboot.
I have tried
ethtool -s eth0 speed 100 duplex full autoneg off
I have tried to add a line to the /etc/sysconfig/network-scripts/ifcfg-eth0 like this:
ETHTOOL_OPTS="speed... (4 Replies)
Discussion started by: bubba112557
4 Replies
4. UNIX for Dummies Questions & Answers
Using Solaris 9 and 10.
What we want to do is set up global rules for our password files to restrict all users, not only new ones set up with the rules but also the ones that have been sitting on the system for years.
Is there a global way to force all users to change their password every 90... (1 Reply)
Discussion started by: LordJezo
1 Replies
5. Shell Programming and Scripting
hi
How can I force user to change of password by modifying the password expiry and the grace period so that the
user has at least 1 week to login and change the password...... (3 Replies)
Discussion started by: tjay83
3 Replies
6. Shell Programming and Scripting
hi
by modifying /etc/shadow
how can I Force a change of password so that user has at least 1 week to login?
I did it by using:
echo "enter username to force password change"
read user;
chage -M 7 $user;
How can I do it by modifying /etc/shadow?? (6 Replies)
Discussion started by: tjay83
6 Replies
7. Red Hat
RHEL 5 update 4. How to force a user to change the password at his next logon.
Thanks in advance. (8 Replies)
Discussion started by: uxadmin007
8 Replies
8. UNIX for Dummies Questions & Answers
I have logged into single user mode and
whenever i issue
passwd root
nothing happens the cursor simply returns back without asking new password.
what can be issue? (5 Replies)
Discussion started by: pinga123
5 Replies
9. Red Hat
Hi expert,
after creating users on Redhat, i wantn to change their password with something that easy to remember and the way we use. For example
#passwd username
hello$123
it don't allow me. It may has something to do /etc/pam.d/filesXXXX there which i don't know to change to allow root... (1 Reply)
Discussion started by: lamoul
1 Replies
10. Forum Support Area for Unregistered Users & Account Problems
I was unable to login and so used the "Forgotten Password' process. I was sent a NEWLY-PROVIDED password and a link through which my password could be changed. The NEWLY-PROVIDED password allowed me to login.
Following the provided link I attempted to update my password to one of my own... (1 Reply)
Discussion started by: Rich Marton
1 Replies
LEARN ABOUT CENTOS
renice
RENICE(1) User Commands RENICE(1)
NAME
renice - alter priority of running processes
SYNOPSIS
renice [-n] priority [-gpu] identifier...
DESCRIPTION
renice alters the scheduling priority of one or more running processes. The first argument is the priority value to be used. The other
arguments are interpreted as process IDs (by default), process group IDs, user IDs, or user names. renice'ing a process group causes all
processes in the process group to have their scheduling priority altered. renice'ing a user causes all processes owned by the user to have
their scheduling priority altered.
OPTIONS
-n, --priority priority
Specify the scheduling priority to be used for the process, process group, or user. Use of the option -n or --priority is optional,
but when used it must be the first argument.
-g, --pgrp pgid...
Force the succeeding arguments to be interpreted as process group IDs.
-u, --user name_or_uid...
Force the succeeding arguments to be interpreted as usernames or UIDs.
-p, --pid pid...
Force the succeeding arguments to be interpreted as process IDs (the default).
-h, --help
Display a help text.
-V, --version
Display version information.
EXAMPLES
The following command would change the priority of the processes with PIDs 987 and 32, plus all processes owned by the users daemon and
root:
renice +1 987 -u daemon root -p 32
NOTES
Users other than the super-user may only alter the priority of processes they own, and can only monotonically increase their ``nice value''
(for security reasons) within the range 0 to PRIO_MAX (20), unless a nice resource limit is set (Linux 2.6.12 and higher). The super-user
may alter the priority of any process and set the priority to any value in the range PRIO_MIN (-20) to PRIO_MAX. Useful priorities are: 20
(the affected processes will run only when nothing else in the system wants to), 0 (the ``base'' scheduling priority), anything negative
(to make things go very fast).
FILES
/etc/passwd
to map user names to user IDs
SEE ALSO
getpriority(2), setpriority(2)
BUGS
Non super-users can not increase scheduling priorities of their own processes, even if they were the ones that decreased the priorities in
the first place.
The Linux kernel (at least version 2.0.0) and linux libc (at least version 5.2.18) does not agree entirely on what the specifics of the
systemcall interface to set nice values is. Thus causes renice to report bogus previous nice values.
HISTORY
The renice command appeared in 4.0BSD.
AVAILABILITY
The renice command is part of the util-linux package and is available from Linux Kernel Archive <ftp://ftp.kernel.org/pub/linux/utils/util-
linux/>.
util-linux September 2011 RENICE(1)