set expiring the password in exactly 90 days.

[Hanry Zhou]

Is there anyway I do that?

By default, it will automatically set to the number of weeks nearing days you specified, in this case it is 12 weeks (84days), not 90 days.
Thanks,

[Dave La Mar]

From the archives-
/sbin/passwd -f -x 42 -n 35 $user
-f is force at next login
-x is max days before have to change
-n is max days between changes
Best of luck.
Regards,
dl

[Steven E. Protter]

MINDAYS=7
MAXDAYS=90

# set up read loop for mass change awk

# passwd -r file -n $MINDAYS -x $MAXDAYS $user

# end of theoretical read look

I do think however it will round up to the nearest week which is 91 days.

SEP

[Chris Watkins_1]

I believe you're stuck with the "rounded to the nearest week" option.
I see the same behaviour on trusted and non-trusted boxen alike.

Someone else may come along and prove me entirely wrong, of course.

[Hanry Zhou]

Steve, Yes, it will set to 91 days, but I want it to be exactly 90days, not 91 or 84 days?

[Dave La Mar]

The archive entries note that rounding to nearest week will happen even though I do not see so in a man of passwd which states "days".
Time to look at some C code.

Regards,
dl

[Dave La Mar]

Found this in an old archive -
The min and max arguments are each represented in units of days.
These arguments will be rounded up to the nearest week on a non-
trusted HP-UX system. If your system is then converted to a trusted
system, the number of days will be based on those weeks. If you only
supply one of the two arguments, passwd checks to see if the other one
already exists. If it does not exist, then it defaults it to zero for
you.

dl

[A. Clay Stephenson · Accepted solution]

This has to do with how the data is actually encoded in the passwd file. One character is used to represent a base-64 digit. Using this encoding scheme the developers faced a choice of 0-63 days or 0-63 weeks or perhaps 0-64 months. They choose weeks as a reasonable compromise given the limited encoding space --- which they themselves had chosen.

[Chris Watkins_1]

You could obviously work around the problem by a bit of scripting.

Have it run every 90 days, and do "passwd -f" against each user
you wanted to force to change their password. Wouldn't be hard.

[Hemanth Gurunath Basrur]

Hello Hanry,

Did you try if you can set 90 days using SAM?

Check this link for info.

http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/5187-2216/5187-2216_top.html&con=/hpux/onlinedocs/5187-2216/00/00/73-con.html&toc=/hpux/onlinedocs/5187-2216/00/00/73-toc.html&searchterms=days&queryid=20031105-200554

Regards,
Hemanth

[doug hosking]

Clay is right. The internal encoding limits the granularity. In standard mode that's weeks. In trusted mode the values are essentially in time_t format, which allows times to be expressed in seconds.