help interpreting usermod man page


 
Thread Tools Search this Thread
Operating Systems Solaris help interpreting usermod man page
# 1  
Old 06-08-2006
help interpreting usermod man page

Hi, I put an expiration on a few id's that I want to remove now. From the man page

-e expire Specify the future date on which a login can no
longer be used; after this date, no user will be
able to access this login. This option is useful
for creating temporary logins. You may type the
value of the argument expire (which is a date) in
any format you like (except a Julian date). For
example, you may enter 10/6/90 or October 6,
1990. A value of " '' defeats the status of the
expired date.

does that mean I issue this command

usermod -e " " username

with a space in between the quotes? Or does the man page mean to leave a blank?

Aaron
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Changing Man page output

I've been asked to come up with a command to display a man page that will continuously scrol (i.e. not hitting space/enter)l. Is there a way do this? I'm stumped. Thank you for your help. (8 Replies)
Discussion started by: Opy99
8 Replies

2. Solaris

man page question

What does the last change means in man page .. does that this man page has not been updated since 2003 or something else ? newfs-options The options are documented in the newfs man page. SunOS 5.10 Last change: 9 Dec 2003 1 System... (2 Replies)
Discussion started by: fugitive
2 Replies

3. Solaris

Unable to get help from man page

Help, it seem that i am unable to get man help form solaris 10. I am running SunOS unknown 5.10 Generic_120012-14 i86pc i386 i86pc when ever i try to man a command what i get is "No manual entry" like the one below. # man grep No manual entry for grep. # man ls No manual entry for ls.... (8 Replies)
Discussion started by: ezsurf
8 Replies

4. UNIX for Advanced & Expert Users

man page issue

Man page is not working my system. It is giving the following the following error > man ls gdbm fatal: read error with debug option > man -d ls ... .... ... ... using less as pager checking for locale en_US add_nls_manpath(): processing /usr/local/man:/usr/share/man:/usr/X11R6/man... (4 Replies)
Discussion started by: praveenkumar_l
4 Replies

5. Red Hat

scp-1.2.27 man page

Hi Guys, I'm looking for the man page for scp version 1.2.27 I have an old redhat server that has a few large scripts that use this version and I want to know what the -A flag does and the man page is not on there. (4 Replies)
Discussion started by: Tornado
4 Replies

6. UNIX for Dummies Questions & Answers

adding a man page

I was wonderiong if ther is a way for a user to add a man page specific to thier account. similar to copying the .1 or .1.gz to /usr/share/man/man1 "cp *.1.gz /usr/share/man/man1". Except for using another folder as I don't have access to /usr/share/man/man1. I would think that this might involve... (1 Reply)
Discussion started by: jacob358
1 Replies

7. UNIX for Dummies Questions & Answers

how do you create a man page?

i've never done this before. i created a script that I placed in /usr/bin, but want to create a man page for it. i'm clueless thanks (3 Replies)
Discussion started by: theDirtiest
3 Replies

8. News, Links, Events and Announcements

Usefull HP-UX Man Page Online

Usefull HP-UX Man Page Online Link LINK: HP-UX Man Page http://www.doc.ic.ac.uk/~mac/manuals/hpux-manual-pages/hpux.man1.html (0 Replies)
Discussion started by: killerserv
0 Replies
Login or Register to Ask a Question
shadow(4)																 shadow(4)

NAME
shadow - shadow password file /etc/shadow is an access-restricted ASCII system file that stores users' encrypted passwords and related information. The shadow file can be used in conjunction with other shadow sources, including the NIS maps passwd.byname and passwd.byuid and the NIS+ table passwd. Programs use the getspnam(3C) routines to access this information. The fields for each user entry are separated by colons. Each user is separated from the next by a newline. Unlike the /etc/passwd file, /etc/shadow does not have general read permission. Each entry in the shadow file has the form: username:password:lastchg:min:max:warn:inactive:expire:flag The fields are defined as follows: username The user's login name (UID). password An encrypted password for the user generated by crypt(3C), a lock string to indicate that the login is not accessible, or no string, which shows that there is no password for the login. The lock string is defined as *LK* in the first four characters of the password field. lastchg The number of days between January 1, 1970, and the date that the password was last modified. The lastchg value is a deci- mal number, as interpreted by atol(3C). min The minimum number of days required between password changes. This field must be set to 0 or above to enable password aging. max The maximum number of days the password is valid. warn The number of days before password expires that the user is warned. inactive The number of days of inactivity allowed for that user. This is counted on a per-machine basis; the information about the last login is taken from the machine's lastlog file. expire An absolute date expressed as the number of days since the Unix Epoch (January 1, 1970). When this number is reached the login can no longer be used. For example, an expire value of 13514 specifies a login expiration of January 1, 2007. flag Failed login count in low order four bits; remainder reserved for future use, set to zero. A value of -1 for min, max, or warn disables password aging. The encrypted password consists of at most CRYPT_MAXCIPHERTEXTLEN characters chosen from a 64-character alphabet (., /, 0-9, A-Z, a-z). Two additional special characters, "$" and ",", can also be used and are defined in crypt(3C). To update this file, use the passwd(1), user- add(1M), usermod(1M), or userdel(1M) commands. In order to make system administration manageable, /etc/shadow entries should appear in exactly the same order as /etc/passwd entries; this includes ``+'' and ``-'' entries if the compat source is being used (see nsswitch.conf(4)). Values for the various time-related fields are interpreted as Greenwich Mean Time. /etc/shadow shadow password file /etc/passwd password file /etc/nsswitch.conf name-service switch configuration file /var/adm/lastlog time of last login See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Stable | +-----------------------------+-----------------------------+ login(1), passwd(1), useradd(1M), userdel(1M), usermod(1M), atol(3C), crypt(3C), crypt_gensalt(3C), getspnam(3C), putspent(3C), nss- witch.conf(4), passwd(4), attributes(5), pam_unix_account(5), pam_unix_auth(5) If password aging is turned on in any name service the passwd: line in the /etc/nsswitch.conf file must have a format specified in the nss- witch.conf(4) man page. If the /etc/nsswitch.conf passwd policy is not in one of the supported formats, logins will not be allowed upon password expiration, because the software does not know how to handle password updates under these conditions. See nsswitch.conf(4) for additional information. 15 Sep 2005 shadow(4)