05-22-2009
changing warning mesage or emailing it
Hi friends
I have a small problem I want to take you opinion in it, I did a password restriction for all users in my server using PAM modules cracklib and using chage command, Now I found that the warning message that appeared to people is not striking enough to people, So I want to change it by big one or email it to people, I know the issue of emailing it may be some hard, for that I pointing to the easy way by changing the password expiration warning message itself, Can any one help me in that.
Thanks
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
We are running an application engine program that sends email to a list of users. In our Test Env, users are able to receive the emails but in our Prod environment, they do not. We are running the same program, and using the same stmp config. any idea on how to troubleshoot? (3 Replies)
Discussion started by: tads98
3 Replies
2. AIX
Morning, All.
Does anyone know how to stop qdaemon from emailing users when print jobs fail?
This is causing a problem as the application that we use is mail-aware; users get a prompt onscreen when they have unread mail in their UNIX account, however they don't all have access to the part of... (2 Replies)
Discussion started by: alexop
2 Replies
3. Shell Programming and Scripting
Hello everybody,
I'm trying to create a script that will cd into a directory and then copy the file with yesterday's date on it and then cd into another directory doing the same thing. Afterwards, i'm trying to zip up the two files, and email them out to people. Can anyone help?
thanks a... (1 Reply)
Discussion started by: jhofilena
1 Replies
4. Shell Programming and Scripting
Hi,
I am having trouble with this script. It is suppose to send me an email when the specified tablespace is 60% full. I run it but nothing happens
FREESPACELOG=/home/oracle/scripts/bin/free_space/freespace.sql
email=bob@bob.edu
subject="PROD: Tablespace Free Space"
cmd="mailx -s... (1 Reply)
Discussion started by: shaseeb
1 Replies
5. Shell Programming and Scripting
hi all,
how do i email a file in the body of an email rather than as an attachment ??
have a ksh script which i need to read a file and email as part of the body rather than an attachment.
my code is :
uuencode file.log | mailx -s "test"
but this sends file as an attachment.
... (2 Replies)
Discussion started by: cesarNZ
2 Replies
6. Shell Programming and Scripting
Hi all,
I have a table like this:
Name email booking no
xyz xyz@abc.com 1235
pqr pqr@abc.com 2536
xyz xyz@abc.com 5896
we have to send a notification to all distinct email ids with consolidated booking information in a single mail.
i.e.,
1235
2536 with some subject has... (6 Replies)
Discussion started by: dineshnarra
6 Replies
7. UNIX for Dummies Questions & Answers
Hi,
Im writing a shell script:
#!/bin/bash
#Send process which has exceeded 25%
#
echo 'pri pid user nice pcpu command' > /export/home/tjmoore/file2
#
if ps -eo pri,pid,user,nice,pcpu,comm | awk '{if($5 >= 25)print $0}' >> /export/home/tjmoore/file2 2>/dev/null
#
#
#
then... (1 Reply)
Discussion started by: jay02
1 Replies
8. AIX
Hi,
I can't get all the enties of AIX .sh_history in email. only first entry of the history is emailed after executing the below code.
mail -s "History `date +%d-%m-%Y`" myemail@xyz.com <$HOME/.sh_history
Can anyone help? (3 Replies)
Discussion started by: m_raheelahmed
3 Replies
9. Shell Programming and Scripting
Hi All,
The following databse table maintains
VENDOR and EMAIL details.
VENOR_NAME VENDOR_EMAIL
DELL surendra@dell.com
HP rajkamal@hp.com
ACER sumathi@acer.com
NOKIA kunal@nokia.com
SONY sinu@sony.com
We have to find emaild id of a vendor based... (7 Replies)
Discussion started by: ROCK_PLSQL
7 Replies
10. Shell Programming and Scripting
I have a script that emails me when I run it manually, but the crontab I'm using must be 'silencing' the output? Here's what I have:
*/15 * * * * /usr/src/blah.sh > /dev/null 2>&1
I don't want it to email me every time it runs, just when I run the sendmail command inside the script if the... (13 Replies)
Discussion started by: unclecameron
13 Replies
LEARN ABOUT XFREE86
chage
CHAGE(1) User Commands CHAGE(1)
NAME
chage - change user password expiry information
SYNOPSIS
chage [options] LOGIN
DESCRIPTION
The chage command 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 his/her password.
OPTIONS
The options which apply to the chage command are:
-d, --lastday LAST_DAY
Set 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).
-E, --expiredate EXPIRE_DATE
Set the date or number of days since January 1, 1970 on which the user's account will no longer be accessible. The date may also be
expressed in the format YYYY-MM-DD (or the format more commonly used in your area). A user whose account is locked must contact the
system administrator before being able to use the system again.
Passing the number -1 as the EXPIRE_DATE will remove an account expiration date.
-h, --help
Display help message and exit.
-I, --inactive INACTIVE
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 user whose account is locked must contact the system administrator before being able to use the system again.
Passing the number -1 as the INACTIVE will remove an account's inactivity.
-l, --list
Show account aging information.
-m, --mindays MIN_DAYS
Set the minimum number of days between password changes to MIN_DAYS. A value of zero for this field indicates that the user may change
his/her password at any time.
-M, --maxdays MAX_DAYS
Set the maximum number of days during which a password is valid. When MAX_DAYS plus LAST_DAY is less than the current day, the user
will be required to change his/her password before being able to use his/her account. This occurrence can be planned for in advance by
use of the -W option, which provides the user with advance warning.
Passing the number -1 as MAX_DAYS will remove checking a password's validity.
-R, --root CHROOT_DIR
Apply changes in the CHROOT_DIR directory and use the configuration files from the CHROOT_DIR directory.
-W, --warndays WARN_DAYS
Set the number of days of warning before a password change is required. The WARN_DAYS option is the number of days prior to the
password expiring that a user will be warned his/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 a shadow password file to be available.
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
his/her password or account is due to expire.
CONFIGURATION
The following configuration variables in /etc/login.defs change the behavior of this tool:
FILES
/etc/passwd
User account information.
/etc/shadow
Secure user account information.
EXIT VALUES
The chage command exits with the following values:
0
success
1
permission denied
2
invalid command syntax
15
can't find the shadow password file
SEE ALSO
passwd(5), shadow(5).
shadow-utils 4.5 01/25/2018 CHAGE(1)