07-09-2003
sh or ksh:
# EDITOR=vi; export EDITOR
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
I have put the following entry in crontab and it is NOT working
1 * * * * && /mybin/myjob.sh
As today is Sep 26th, Iam using NF-4 to test.
Thanks (2 Replies)
Discussion started by: baanprog
2 Replies
2. UNIX for Advanced & Expert Users
Dear all
We have SunOS 5.10 Generic_127127-11 sun4u sparc SUNW,Sun-Fire-V250
i have scheduled cronjob but its not working
Crontab details
15 15 * * * /d5/oratest/testdb/hotbackup_new.sh TEST247
15 15 * * * mkdir -p rajesh /d4/appltest
Crontab log details
> CMD: mkdir... (4 Replies)
Discussion started by: rajesh_hv
4 Replies
3. Solaris
I have a script which name is sicaklik.sh
It is in the root directory.
I can run manually but I want to run automatically every 3 minutes but it is not working. WHY?
#whoami
root
#crontab -l
#ident "@(#)root 1.21 04/03/23 SMI"
3 * * * * sh ./sicaklik.sh
#ls -l sicaklik*... (6 Replies)
Discussion started by: getrue
6 Replies
4. UNIX for Dummies Questions & Answers
Hi,
I had setup crontab to execute my script every day midnight 00:00
Below are the current settings.
crontab -l
0 0 * * * /apps/bin/compress.ksh_moht > /dev/null 2>&1
Should it not work?
I need help fix this? (8 Replies)
Discussion started by: shifahim
8 Replies
5. Red Hat
I can run manually script of ntopdump.sh but crontab can't run this script very five minutes.
# crontab -l
*/3 * * * * root sh /root/ping.sh
*/5 * * * * root sh /root/ntopdump.sh
#
# pwd
/root
# ls -l
total 88
-rwxrwxr-x 1 root root 1645 Jun 14 19:01 anaconda-ks.cfg
drwxrwxr-x 2 root... (14 Replies)
Discussion started by: getrue
14 Replies
6. Solaris
Shell = ksh
Hi all,
I scheduled an automated job on my application server like below,
30 13 * * 1-5 $HOME/my_script.sh
However the script was not executed as expected. Any reason that may cause this to happen? (6 Replies)
Discussion started by: isaacniu
6 Replies
7. UNIX for Advanced & Expert Users
Hi,
When I set the crontab to run every minute, every hour, it works fine.
* * * * * env > /tmp/env.output
However I want to run it every day at 8:00 AM and it does not run.
* 8 * * * env > /tmp/env.output
I ran the 'date' command which says it's 8AM PST and also the 'TZ'... (0 Replies)
Discussion started by: samantha13
0 Replies
8. Linux
Hi,
I know this is a common topic. I'm trying to launch a perl script using a contab -e entry. I've been trying diff options but nothing seems to work:
My cron is running:
UID PID PPID C STIME TTY TIME CMD
root 3755 1 0 Nov27 ? 00:00:00 crond
This... (4 Replies)
Discussion started by: krebe
4 Replies
9. Shell Programming and Scripting
Hi All,
I have a script with deatils as :
$ ls -ld catch_logs.sh
-rwx--x--x 1 muser muser 752 Jun 5 22:36 catch_logs.sh
User crontab looks likes:
$ crontab -l
SHELL=/bin/bash
PATH=/sbin:/bin:/usr/sbin:/usr/bin
* * * * * /opt/scripts/catch_logs.sh
Now if I run this script... (7 Replies)
Discussion started by: Junaid Subhani
7 Replies
10. Red Hat
Dear Friends,
I have Red Hat Linux Enterprise version 6.3. running SAP and oracle.
I have created one crontab for user orasid to execute one job periodically.
But it is not executing. I have checked crontab service is running.
Please help in the matter.
Regards,
Bhagawati Pandey (5 Replies)
Discussion started by: BPANDEY
5 Replies
VIPW(8) BSD System Manager's Manual VIPW(8)
NAME
vipw -- edit the password file
SYNOPSIS
vipw [-d directory]
DESCRIPTION
The vipw utility edits the password file after setting the appropriate locks, and does any necessary processing after the password file is
unlocked. If the password file is already locked for editing by another user, vipw will ask you to try again later. The default editor for
vipw is vi(1).
When run without options, vipw will work with the password files in /etc. The -d option may be used to specify an alternative directory to
work with.
The vipw utility performs a number of consistency checks on the password entries, and will not allow a password file with a ``mangled'' entry
to be installed. If vipw rejects the new password file, the user is prompted to re-enter the edit session.
Once the information has been verified, vipw uses pwd_mkdb(8) to update the user database. This is run in the background, and, at very large
sites could take several minutes. Until this update is completed, the password file is unavailable for other updates and the new information
is not available to programs.
ENVIRONMENT
If the following environment variable exists it will be utilized by vipw:
EDITOR The editor specified by the string EDITOR will be invoked instead of the default editor vi(1). This can be used to allow a
script to non-interactively modify the password file.
PW_SCAN_BIG_IDS See pwd_mkdb(8).
SEE ALSO
chpass(1), passwd(1), passwd(5), adduser(8), pw(8), pwd_mkdb(8)
HISTORY
The vipw utility appeared in 4.0BSD.
BUGS
The mechanism for checking for password file modifications requires that the modification time of the password file changes. This means that
in a default configuration where file system timestamps are not calculated with sub-second precision, EDITOR has to run for at least one sec-
ond. Non-interactive editor scripts should invoke sleep(1) or equivalent to ensure this happens.
BSD
February 14, 2012 BSD