09-16-2008
I can see the post, but it is disconnected from the thread and I don't know what thread it was. Your post says "maybe this will help you out" and then it seems to be a link to your blog entry describing cron.
Everyone who has a blog with an entry descibing some aspect of unix will drop by the site, find a thread that roughly matches the blog entry and then create a post like that. We tend to remove the posts and issue an infraction. We aren't trying to create a directory of blogs here. Please don't answer a question on your site and just post a link. Put the answer here. Our search function can find it and we don't need to keep checking the link to see if it valid. Most of the linked answers that we did allow in the early years are now dead links.
8 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello all! I am praying someone can help me. I have been trying to install dual nics on my FreeBSD box. In my attempts I edited my RC.CONF file. I must have editing something wrong, because during the boot sequence, my machine gets through bringing up most of the services then it stops and gets... (5 Replies)
Discussion started by: ezekiel61
5 Replies
2. Linux
If i want to display a banner that says Happy Bday, but I want to put that output banner into a file called bday4me,
could I use the command (echo) or (banner -w35) Happy Bday >> bday4me
would this command work? Sorry for asking, but i'm at home just now and don't have access to a UNIX... (3 Replies)
Discussion started by: Cisco
3 Replies
3. Shell Programming and Scripting
Dear all,
When I tried to run receive.sh,it returned following errors.
syntax error near unexpected token `do
#!/usr/bin/ksh
GlobalValueReceive=r
GlobalValueWorking=w
GlobalValueTemp=t
$exec 0<Property
while read LineInProperty
do
if
then
$GlobalValueReceive =... (8 Replies)
Discussion started by: joshuaduan
8 Replies
4. UNIX for Dummies Questions & Answers
hi everyone im new here and im hoping you could help me out here. Yesterday i removed a time stamp from a program that i am using.This timestamp should contain a date of 04/04/2008 with a time sometime in that day.
the stamp in hex is 7C FE 2B 04 DA 4E E3 40
ive looked everywhere and im... (1 Reply)
Discussion started by: uselessprog
1 Replies
5. Shell Programming and Scripting
This piece of code is in a shell script I'm trying to modify to run on my system.
sed s:nu\\t.\*:"nu=0"
It's clearly a substitute script which replaces nu\\t.\* with nu = 0.
What exactly does nu\\t.\* demarcate though-- I thought it was just the previous nu = xxxxx (which existed and is... (3 Replies)
Discussion started by: czar21
3 Replies
6. Linux
I tried to run nohup command line on my Linux server to connect to a remote server, then execute Oracle binary to run a process at background. My Linux information looks like this:
oracle@myserver:/opt/oracle/scripts
$ uname -a
Linux myserver.domain.com 2.6.18-194.32.1.0.1.el5 #1 SMP Tue Jan 4... (1 Reply)
Discussion started by: duke0001
1 Replies
7. Shell Programming and Scripting
> reverse=`tput rev`
> revert=`tput sgr0`
> var="This is some note."
> echo $var
This is some note.
> var2="This is ${reverse}some${revert} note."
> echo $var2
This is some note.
> var3=$(echo $var | sed 's/some/${reverse}some${revert}/g')
> echo $var3
This is... (3 Replies)
Discussion started by: adamreiswig
3 Replies
8. UNIX for Beginners Questions & Answers
Hello... And thanks in advance for any help anyone can offer me
I was trying to work out the differences between displaying modify, access, and change times with the 'ls' command. Everything seems in order when I look at files, but the access time on a directory doesn't seem to change when I... (4 Replies)
Discussion started by: bodisha
4 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)