03-12-2010
If the expire value has made its way into the /etc/shadow file then it should be preserved between password changes.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
login: TEST7
TEST7's Password:
Your password will expire: Wed Feb 19 14:28:08 2003
How can I the same information become in a script (as example
in the .profile)?????????
My login starts with .profile. These File is a menue with 24 lines and the message " Your password ....." disappear
to... (8 Replies)
Discussion started by: Erwin Stocker
8 Replies
2. Shell Programming and Scripting
Dear friends..
Our project has a module that runs on handheld devices. Through the handheld we telnet to solaris where the application actually runs. I noticed that after starting a session through the handheld, if i go out of range or if i remove and replace the battery in the handheld, the... (1 Reply)
Discussion started by: deepsteptom
1 Replies
3. Shell Programming and Scripting
Hi,
Is there any way to find out the UNIX user's password expire date?. It'll we helpful to inform the users to change the password before it get expires.(FYI - I am not having only admin previlege.) (1 Reply)
Discussion started by: sharif
1 Replies
4. Solaris
Hello
I want to set the password for user never expire through the command line. For your information the box is running under Solaris 8 platform. (2 Replies)
Discussion started by: shamsul
2 Replies
5. Red Hat
Hi All,
Is this true on chage command?
-M, MAX_DAYS
Passing the number -1 as MAX_DAYS will remove checking a password's validity.
Does this means password will not expire anymore?
Thanks for any comment you may add. (0 Replies)
Discussion started by: itik
0 Replies
6. UNIX for Advanced & Expert Users
Hi,
I am using sftp in batch script for which all configuration for public/private keys are done and it works fine without asking a password. No issues till this point. Now I the problem I have is that if the password expires/someone changes the authentication keys at reote server then the... (4 Replies)
Discussion started by: coolwade
4 Replies
7. Solaris
Hi All,
I have Solaris 9 and there is user created in that server called appuser
That user should to be never expire..
can anyone advice me how can I modify that user to be never expire thru the command line without using GUI tool. (1 Reply)
Discussion started by: Mr.AIX
1 Replies
8. AIX
Does anyone know if the default message displayed when a users password has expired can be changed? I am just assuming the message below is the default one. If so please tell.
Using username "justinxx".
justinxx@160.23.12.44's password:
WARNING: Your password has expired.
You must... (2 Replies)
Discussion started by: juredd1
2 Replies
9. Shell Programming and Scripting
I have a program that outputs a file on the number days left before software license expired. It reads in a text file name expiredt.txt.
expiredt.txt contents are as follows:
EM software 30NOV2015 11/30/2015
ABM software 30NOV2015 11/30/2015
ABM software ... (2 Replies)
Discussion started by: dellanicholson
2 Replies
10. Solaris
Hi There,
Actually I'm looking for command in Solaris 11 for the following
Command to do User Never Expire.
Command to return the user Expire to normal mode.
Command to do User Never Lock.
Command to return the user Never Lock to normal mode.
Please advice .. (1 Reply)
Discussion started by: roooooooooot
1 Replies
IPL(4) Kernel Interfaces Manual IPL(4)
NAME
ipl - IP packet log device
DESCRIPTION
The ipl pseudo device's purpose is to provide an easy way to gather packet headers of packets you wish to log. If a packet header is to be
logged, the entire header is logged (including any IP options - TCP/UDP options are not included when it calculates header size) or not at
all. The packet contents is also logged after the header.
Prepending every packet header logged is a structure containing information relevant to the packet following and why it was logged. The
structure's format is as follows:
struct ipl_ci {
u_long sec; /* time when the packet was logged */
u_long usec;
u_long plen; /* length of packet data logged */
u_short hlen; /* length of headers logged */
u_short rule; /* rule number (for log ...) or 0 if result = log */
u_long flags:24; /* XXX FIXME do we care about the extra bytes? */
#if (defined(OpenBSD) && (OpenBSD <= 1991011) && (OpenBSD >= 199606))
u_long filler:8; /* XXX FIXME do we care? */
u_char ifname[IFNAMSIZ];
#else
u_long unit:8;
u_char ifname[4];
#endif
};
In the case of the header causing the buffer to finish on a non-32bit
boundary, padding will be `appended' to ensure that the next log entry
is aligned to a 32bit boundary.
If the packet contents is more then 128 bytes, then only 128 bytes of the
packet contents is logged. Should the packet contents finish on a non-32bit
boundary, then the last few bytes are not logged to ensure the log entry
is aligned to a 32bit boundary.
ipl is a read-only (sequential) character pseudo-device.
The ioctls which are loaded with this device can be found under ipf(4).
The only ioctl which is used for logging and doesn't affect the filter is:
ioctl(fd, SIOCIPFFB, int *)
This ioctl flushes the log buffer and returns the number of bytes flushed.
There is currently no support for non-blocking IO with this device, meaning all read operations should be considered blocking in nature (if
there is no data to read, it will sleep until some is made available).
SEE ALSO
ipf(4)
BUGS
Packet headers are dropped when the internal buffer (static size) fills.
FILES
/dev/ipl0
IPL(4)