12-07-2005
set EDITOR=vi -> default editor not setting for cron tab
Hi All,
I am running a script , working very fine on cmd prompt. The problem is that when I open do crontab -e even after setting editor to vi by
set EDITOR=vi it does not open a vi editor , rather it do as below.....
/////////////////////////////////////////////////////
$ set EDITOR=vi
$ echo $EDITOR
$ crontab -e
79
29 16 * * * /bin/sh /app/siebel/testdir/automate.sh
?
The crontab file was not changed.
$
///////////////////////////////////////////////////////////
Even if i do ,
$vi crontab
it opens a vi editor for me with name crontab ,
where I can write the above line
29 16 * * * /bin/sh /app/siebel/testdir/automate.sh
and save . But it is not showing me the crontab job when I do
$crontab -l
Can some bdy help me for this ..
PS : I have also tried
$setenv EDITOR vi
but in vain, still getting no results. Really need your help for this.....
Thanks & Regards,
Aru
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Redhat 9
I want to change my default text editor from vi to pico.
When I look in the .bash_profile or .bashrc I do not see the EDITOR variable. So how do I change the default permanently? (1 Reply)
Discussion started by: Tony Empire
1 Replies
2. AIX
For some reason something has changing in my AIX environment where when I type:
ACLEDIT filename
...I get:
3002-104 acledit: EDITOR environment variable must be full pathname
I know I need to reset the EDITOR variables path to /usr/bin/vi but I can't remember the syntax anyone? (2 Replies)
Discussion started by: heprox
2 Replies
3. Solaris
Hi all
I am new to this forum (just registered)
I need help from you guys
Even if it is a basic question please don't hesitate to answer.Any answer will be helpful to me
I am unable to get the previously entered commands by pressing uparrow
When i enered uparrow it is giving ^[[A
I got... (2 Replies)
Discussion started by: oracle_sri
2 Replies
4. Solaris
hi guys , i need some help
i want to set cron job for every sunday , of each month so any body plz help or this proble :confused: (1 Reply)
Discussion started by: Kbharat20
1 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I knw its a silly question, but am a newbie to 'vi' editor. I'm forced to use this, hence kindly help me with this question.
How can i paste a chunk 'copied from' a different editor(gedit) in 'vi editor'?
As i see, p & P options does work only within 'vi'. (10 Replies)
Discussion started by: harishmitty
10 Replies
6. Solaris
Epic Editor was not able to obtain a license for your use. Feature Epic Editor :License server is down (1 Reply)
Discussion started by: durgaprasadr13
1 Replies
7. Solaris
I am setting the size using "stty columns 120" . But I still get the prompt saying "terminal too wide " when I am in vi.
is there any time limit for this setting?
how to set the column size to 120 permanently?
Thanks in advance,
Devi (4 Replies)
Discussion started by: pvkdevi
4 Replies
8. UNIX for Dummies Questions & Answers
Guys,
Can somebody help in setting vi as the default editor in zsh shell.
I know that in ksh and bourne we can achieve the setting through .profile file.
I want to replicate the behavior of ksh in zsh where on command prompt when one presses escape the screen acts as a vi.
And one can use all... (1 Reply)
Discussion started by: yabhi_22
1 Replies
9. UNIX for Dummies Questions & Answers
Hi ,
Below is the content of my .profile
$cat .profile
# Workstation users: Make changes to your .profile file in your home dir.
. /.profile
set -o vi
PS1=$
But anytime I login I have to source "set -o vi" separately.Please suggest (8 Replies)
Discussion started by: ramesh12621
8 Replies
10. UNIX Desktop Questions & Answers
Hello All,
Last night I installed OpenSuSE 12.1 (i586) on a HP Mini 110 laptop. And I selected GNOME as my Desktop during install...
So I was trying to customize some things about the desktop, for example adding the Maximize/Minimize/Close options to the titlebar of a window.
I did this... (2 Replies)
Discussion started by: mrm5102
2 Replies
LEARN ABOUT MOJAVE
crontab
CRONTAB(1) BSD General Commands Manual CRONTAB(1)
NAME
crontab -- maintain crontab files for individual users (V3)
SYNOPSIS
crontab [-u user] file
crontab [-u user] { -l | -r | -e }
DESCRIPTION
The crontab utility is the program used to install, deinstall or list the tables used to drive the cron(8) daemon in Vixie Cron. Each user
can have their own crontab, and they are not intended to be edited directly.
(Darwin note: Although cron(8) and crontab(5) are officially supported under Darwin, their functionality has been absorbed into launchd(8),
which provides a more flexible way of automatically executing commands. See launchctl(1) for more information.)
If the /usr/lib/cron/cron.allow file exists, then you must be listed therein in order to be allowed to use this command. If the
/usr/lib/cron/cron.allow file does not exist but the /usr/lib/cron/cron.deny file does exist, then you must not be listed in the
/usr/lib/cron/cron.deny file in order to use this command. If neither of these files exists, then depending on site-dependent configuration
parameters, only the super user will be allowed to use this command, or all users will be able to use this command. The format of these
files is one username per line, with no leading or trailing whitespace. Lines of other formats will be ignored, and so can be used for com-
ments.
The first form of this command is used to install a new crontab from some named file or standard input if the pseudo-filename '-' is given.
The following options are available:
-u Specify the name of the user whose crontab is to be tweaked. If this option is not given, crontab examines ``your'' crontab, i.e.,
the crontab of the person executing the command. Note that su(1) can confuse crontab and that if you are running inside of su(1) you
should always use the -u option for safety's sake.
-l Display the current crontab on standard output.
-r Remove the current crontab.
-e Edit the current crontab using the editor specified by the VISUAL or EDITOR environment variables. The specified editor must edit
the file in place; any editor that unlinks the file and recreates it cannot be used. After you exit from the editor, the modified
crontab will be installed automatically.
FILES
/usr/lib/cron/cron.allow
/usr/lib/cron/cron.deny
DIAGNOSTICS
A fairly informative usage message appears if you run it with a bad command line.
SEE ALSO
crontab(5), compat(5), cron(8), launchctl(1)
STANDARDS
The crontab command conforms to IEEE Std 1003.2 (``POSIX.2''). The new command syntax differs from previous versions of Vixie Cron, as well
as from the classic SVR3 syntax.
AUTHORS
Paul Vixie <paul@vix.com>
BSD
December 29, 1993 BSD