cron on 10.5.2 server

In article <bob-E4827D.22442724042008@[199.45.49.11]>,
Robert Peirce <bob.TakeThisOut@peirce-family.com.invalid> wrote:

> In article <nospam.News.Bob-FC333A.21423324042008.TakeThisOut@news.verizon.net>,
> Bob Harris <nospam.News.Bob.TakeThisOut@remove.Smith-Harris.us> wrote:
>
> > OK, some suggestions:
> >
> > 1) Modify your own .vimrc to specify your own nowritebackup
> >
> > autocmd BufReadPre,FileReadPre crontab.* set nowritebackup
> >
> > NOTE 1: I am setting the value when the file is read,
> > NOT when it is written.
> >
> > NOTE 2: I did NOT specify a directory path.
> > I just said any file that starts with
> > crontab.* is treated this way.
> >
> > 2) Make the above modification to /usr/share/vim/vimrc
>
> This works! Thanks, so much. I tried it first in my own .vimrc file
> then I put it in the system file.
>
> I have been reviewing the vim help on "events." Actually seeing this
> really helped a lot.
>
> Now I am wondering why BufReadPre and FileReadPre work but BufWrite does
> not. BufWrite is supposed to apply before writing, but there must be
> some kind of delay operating that is preventing this. Anyhow, you got it
> working for me and I appreciate it.

/usr/share/vim/vimrc specified /private/tmp/crontab.*, however,
when I was doing my testing, I noticed that Vim thought the file
was stored in /tmp/crontab.*

I am assuming that the real root of the problem is that they
changed the behavior of crontab -e to use a different path for the
file being edited. But no one thought to fix the
/usr/share/vim/vimrc file.

Bob Harris
 >> Stay informed about: cron on 10.5.2 server 

In article <bob-E4827D.22442724042008@[199.45.49.11]>,
Robert Peirce <bob.TakeThisOut@peirce-family.com.invalid> wrote:

> In article <nospam.News.Bob-FC333A.21423324042008.TakeThisOut@news.verizon.net>,
> Bob Harris <nospam.News.Bob.TakeThisOut@remove.Smith-Harris.us> wrote:
>
> > OK, some suggestions:
> >
> > 1) Modify your own .vimrc to specify your own nowritebackup
> >
> > autocmd BufReadPre,FileReadPre crontab.* set nowritebackup
> >
> > NOTE 1: I am setting the value when the file is read,
> > NOT when it is written.
> >
> > NOTE 2: I did NOT specify a directory path.
> > I just said any file that starts with
> > crontab.* is treated this way.
> >
> > 2) Make the above modification to /usr/share/vim/vimrc
>
> This works! Thanks, so much. I tried it first in my own .vimrc file
> then I put it in the system file.
>
> I have been reviewing the vim help on "events." Actually seeing this
> really helped a lot.
>
> Now I am wondering why BufReadPre and FileReadPre work but BufWrite does
> not. BufWrite is supposed to apply before writing, but there must be
> some kind of delay operating that is preventing this. Anyhow, you got it
> working for me and I appreciate it.

I've submitted a bug report to Apple on /usr/share/vim/vimrc

<https://bugreport.apple.com/cgi-bin/WebObjects/RadarWeb.woa/54/wo/
IAMOWvqjyfWBzJsdhN6M4w/11.21>

Bob Harris
 >> Stay informed about: cron on 10.5.2 server 

In article <nospam.News.Bob-EE7E05.18430925042008.RemoveThis@news.verizon.net>,
Bob Harris <nospam.News.Bob.RemoveThis@remove.Smith-Harris.us> wrote:

> In article <bob-E4827D.22442724042008@[199.45.49.11]>,
> Robert Peirce <bob.RemoveThis@peirce-family.com.invalid> wrote:
>
> > In article <nospam.News.Bob-FC333A.21423324042008.RemoveThis@news.verizon.net>,
> > Bob Harris <nospam.News.Bob.RemoveThis@remove.Smith-Harris.us> wrote:
> >
> > > OK, some suggestions:
> > >
> > > 1) Modify your own .vimrc to specify your own nowritebackup
> > >
> > > autocmd BufReadPre,FileReadPre crontab.* set nowritebackup
> > >
> > > NOTE 1: I am setting the value when the file is read,
> > > NOT when it is written.
> > >
> > > NOTE 2: I did NOT specify a directory path.
> > > I just said any file that starts with
> > > crontab.* is treated this way.
> > >
> > > 2) Make the above modification to /usr/share/vim/vimrc
> >
> > This works! Thanks, so much. I tried it first in my own .vimrc file
> > then I put it in the system file.
> >
> > I have been reviewing the vim help on "events." Actually seeing this
> > really helped a lot.
> >
> > Now I am wondering why BufReadPre and FileReadPre work but BufWrite does
> > not. BufWrite is supposed to apply before writing, but there must be
> > some kind of delay operating that is preventing this. Anyhow, you got it
> > working for me and I appreciate it.
>
> /usr/share/vim/vimrc specified /private/tmp/crontab.*, however,
> when I was doing my testing, I noticed that Vim thought the file
> was stored in /tmp/crontab.*
>
> I am assuming that the real root of the problem is that they
> changed the behavior of crontab -e to use a different path for the
> file being edited. But no one thought to fix the
> /usr/share/vim/vimrc file.

I had /private/tmp linked to /tmp. I picked that up in 10.4. I ran
into a problem with some other program that had the same situation. Now
I can't remember what it was. I guess I didn't realize I was also
fixing cron!

More importantly, I got the original version of vimrc to work. I first
tried your idea of removing the path and that worked. Then I put the
path back in and it worked. The only thing I can figure is I must have
had an unprintable character buried somewhere in the path and it got
removed when I was playing with it.

I really appreciate everybody's help. It looks like everything is back
together and working the way it is supposed to work.

--
Robert B. Peirce, Venetia, PA 724-941-6883
bob AT peirce-family.com [Mac]
rbp AT cooksonpeirce.com [Office]
 >> Stay informed about: cron on 10.5.2 server 

[[This message is not archived, and is only displayed for one month past post date.]]

In message <bob-13D938.09335222042008@[199.45.49.11]>
Robert <bob.TakeThisOut@peirce-family.com.invalid> wrote:
> In article <20080422050407.GD39909@fuchs>,
> AndrŽ Berger <andre.berger.TakeThisOut@web.de> wrote:
>> I think one would have to ":set noswap" in vim

> That is an "unknown option" in vi.

And that has wheat to do with setting it in *vim*??

Nothing?

Right.

--
I got a question. If you guys know so much about women, how come you're here
at like the Gas 'n' Sip on a Saturday night completely alone drinking
beers with no women anywhere?
 >> Stay informed about: cron on 10.5.2 server 

[[This message is not archived, and is only displayed for one month past post date.]]

In message <jollyroger-482AD1.16064124042008.DeleteThis@individual.net>
Jolly <jollyroger.DeleteThis@pobox.com> wrote:
> We're talking about using crontab to edit cron tables, and vi/vim has
> beeen the default editor for crontab for, like forever.

Except when it's not.

crontab actually has no default editor, it simply uses the EDITOR
defined in your environment settings.

crontab is a little retarded with the whole swapfile issue, and that can
be an issue in any EDITOR that does the 'right thing' and has you work
and edit a swapfile instead of the original. Most other utilities
(visudo, for example) do not have this retarded behavior.

And yeah, I now it's supposed to be more secure. And in some marginal
edge case, I'm sure it is. 99.999% of the time, it's just an annoyance
though.


--
It was a fifty-four with a mashed up door and a cheesy little amp with a sign
on the front said "Fender Champ" and a second-hand guitar it was a
Stratocaster with a whammy bar
 >> Stay informed about: cron on 10.5.2 server 

On Fri, 02 May 2008 08:19:31 -0500, Lewis
<g.kreme RemoveThis @gmail.com.dontsendmecopies> wrote:

>> We're talking about using crontab to edit cron tables, and vi/vim has
>> beeen the default editor for crontab for, like forever.
>
>Except when it's not.
>
>crontab actually has no default editor, it simply uses the EDITOR
>defined in your environment settings.

If someone is not interested in using Unix, won't use vi, but does use
crontab - where should he put his .bash_profile or .bashrc file
(created with textedit), and should the EDITOR= command look like, &
what should he name it?

(This is a real question which I did not feel qualified to answer)
 >> Stay informed about: cron on 10.5.2 server 

In article <slrng1m573.5pj.g.kreme.DeleteThis@cerebus.local>,
Lewis <g.kreme.DeleteThis@gmail.com.dontsendmecopies> wrote:

> In message <jollyroger-482AD1.16064124042008.DeleteThis@individual.net>
> Jolly <jollyroger.DeleteThis@pobox.com> wrote:
> > We're talking about using crontab to edit cron tables, and vi/vim has
> > beeen the default editor for crontab for, like forever.
>
> Except when it's not.
>
> crontab actually has no default editor, it simply uses the EDITOR
> defined in your environment settings.

And the default EDITOR on most *nix systems is... *drum roll* ; )

--
Please send all responses to the relevant news group. E-mail sent to
this address may be devoured by my very hungry SPAM filter. I do not
read posts from Google Groups. Use a real news reader if you want me to
see your posts.

JR
 >> Stay informed about: cron on 10.5.2 server 

In article <b0bm14pqggf0j0fh3eep19p7hej7hadl6t DeleteThis @4ax.com>,
Howard Brazee <howard DeleteThis @brazee.net> wrote:

> On Fri, 02 May 2008 08:19:31 -0500, Lewis
> <g.kreme DeleteThis @gmail.com.dontsendmecopies> wrote:
>
> >> We're talking about using crontab to edit cron tables, and vi/vim has
> >> beeen the default editor for crontab for, like forever.
> >
> >Except when it's not.
> >
> >crontab actually has no default editor, it simply uses the EDITOR
> >defined in your environment settings.
>
> If someone is not interested in using Unix, won't use vi, but does use
> crontab - where should he put his .bash_profile or .bashrc file
> (created with textedit), and should the EDITOR= command look like, &
> what should he name it?
>
> (This is a real question which I did not feel qualified to answer)

I'm not so sure you really can use a GUI editor to edit cron tables. I
just tried with EDITOR set to TextWrangler's 'edit' command-line tool,
and it exited immediately with:

export EDITOR=/usr/bin/edit
# echo $EDITOR
/usr/bin/edit
# crontab -e
crontab: no changes made to crontab

Not to mention, I fail to see why you'd even *want* to edit Unix cron
tables with a GUI editor... Anyhow, I'll disregard that and assume you
really do want to change your editor to a GUI tool...

If you're going to create any Unix configuration files with TextEdit,
you'd better make damned sure you are saving the file as *Plain Text*
and with *Unix* line breaks. If TextEdit can;t do this, don't even
bother running TextEdit.

Personally, I'd just skip TextEdit completely and use a plain text
editor that is designed for editing such files, like TextWrangler, which
is free anyway, optionally installs an 'edit' command-line tool that
allows TextWrangler to function as a replacement to various command-line
editors.

..bashrc and .bash_profile both belong in your home directory
(/Users/you). So open TextWrangler, and choose File > Open Hidden from
the menu bar to look and see if you already have a ~/.bashrc or
~/.bash_profile.

If you already have these files, set TextWrangler's Open dialog box
"Enable" menu to "All", then open the .bashrc file.

If you don't have .bash_profile, create a new document that has this
content:

export ENV=~/.bashrc

if test -f ~/.bashrc; then
. ~/.bashrc
fi

Save the file as ".bash_profile" in your home folder, and be sure to
click the Options button in the Save dialog box to specify you want
*Unix* Line Breaks - otherwise the system will not read the file
correctly.

If you *do* have .bash_profile, just make sure it contains the code
above so your .bashrc will be source properly.

If you don't have .bashrc, create a new blank document. If you *do* have
..bashrc, you can just open it and add to the end of it. You'll want to
add a line to your .bashrc file that says:

export EDITOR=/usr/bin/edit

Save as plain text with Unix line breaks. When you are done, close and
re-open a terminal window. To verify your changes worked, type:

echo $EDITOR

You should see the path to 'edit' echoed back to you, like this:

# echo $EDITOR
/usr/bin/edit

--
Please send all responses to the relevant news group. E-mail sent to
this address may be devoured by my very hungry SPAM filter. I do not
read posts from Google Groups. Use a real news reader if you want me to
see your posts.

JR
 >> Stay informed about: cron on 10.5.2 server 

On Fri, 02 May 2008 14:24:50 -0500, Jolly Roger <jollyroger.RemoveThis@pobox.com>
wrote:

>Personally, I'd just skip TextEdit completely and use a plain text
>editor that is designed for editing such files, like TextWrangler, which
>is free anyway, optionally installs an 'edit' command-line tool that
>allows TextWrangler to function as a replacement to various command-line
>editors.

I did mention that - I'll push it. Thanks (for the rest of the
message as well).
 >> Stay informed about: cron on 10.5.2 server 

On Fri, 02 May 2008 14:24:50 -0500, Jolly Roger <jollyroger DeleteThis @pobox.com>
wrote:

>Personally, I'd just skip TextEdit completely and use a plain text
>editor that is designed for editing such files, like TextWrangler, which
>is free anyway, optionally installs an 'edit' command-line tool that
>allows TextWrangler to function as a replacement to various command-line
>editors.
>
>.bashrc and .bash_profile both belong in your home directory
>(/Users/you). So open TextWrangler, and choose File > Open Hidden from
>the menu bar to look and see if you already have a ~/.bashrc or
>~/.bash_profile.

On my computer (not the computer of the guy who wanted my help) I
opened TextWrangler and found a .bash_history and a bash_profile file
(in HBrazee). The latter I created myself and it consists of one
line saying:
ls

I was hoping that when I started Terminal, I would see ls run, but
nothing happens. So I try running it (obviously incorrectly):

Last login: Thu May 1 19:48:45 on console
bHoward-Brazees-Computer:~ HBrazee$ bash_profile
-bash: bash_profile: command not found
Howard-Brazees-Computer:~ HBrazee$
 >> Stay informed about: cron on 10.5.2 server 

In article <ru2n141sc4cosquiqrhgin3o83uiqc4otq RemoveThis @4ax.com>,
Howard Brazee <howard RemoveThis @brazee.net> wrote:

> On Fri, 02 May 2008 14:24:50 -0500, Jolly Roger <jollyroger RemoveThis @pobox.com>
> wrote:
>
> >Personally, I'd just skip TextEdit completely and use a plain text
> >editor that is designed for editing such files, like TextWrangler, which
> >is free anyway, optionally installs an 'edit' command-line tool that
> >allows TextWrangler to function as a replacement to various command-line
> >editors.
> >
> >.bashrc and .bash_profile both belong in your home directory
> >(/Users/you). So open TextWrangler, and choose File > Open Hidden from
> >the menu bar to look and see if you already have a ~/.bashrc or
> >~/.bash_profile.
>
> On my computer (not the computer of the guy who wanted my help) I
> opened TextWrangler and found a .bash_history and a bash_profile file
> (in HBrazee). The latter I created myself and it consists of one
> line saying:
> ls
>
> I was hoping that when I started Terminal, I would see ls run, but
> nothing happens. So I try running it (obviously incorrectly):
>
> Last login: Thu May 1 19:48:45 on console
> bHoward-Brazees-Computer:~ HBrazee$ bash_profile
> -bash: bash_profile: command not found
> Howard-Brazees-Computer:~ HBrazee$

You need to learn more about the commind-line environment. ; )

1. The BASH profile file should be named .bash_profile - note the period
character at the beginning. If the file is not named correctly, and does
not exist in your home folder, BASH will not read it.

2. Why are you trying to run a script? My instructions showed you how to
set up .bash_profile and .bashrc - those are not your average, ordinary
shell scripts - in the sense that the BASH environment looks
specifically for these files during initialization of your shell
session. In other words, there are certain things that are appropriate
to put in these files, and 'ls' isn't one of them. If you want to write
a script, you really shouldn't use a name like .bash_profile, because
that name is reserved for BASH in this context. Instead, call it
something like "my_script.sh". The ".sh" filename extension denotes
shell scripts.

3. If you create a script file from scratch, chances are it won't be
executable by you or any other user or group until you make it so. To
make a script file executable, you would need to issue the 'chmod +x
/path/to/script' command.

4. To run any executable file (including a shell script) that is not in
one of the paths listed in your PATH environment variable, you'll need
to (a) use 'cd' to change to the directory containing the executable
file, then (b) issue the './scriptname.sh' command to run it from within
the current directory. Remember, on the command line, . means "the
current directory, just as .. means "the parent of the current
directory".

--
Please send all responses to the relevant news group. E-mail sent to
this address may be devoured by my very hungry SPAM filter. I do not
read posts from Google Groups. Use a real news reader if you want me to
see your posts.

JR
 >> Stay informed about: cron on 10.5.2 server 

On Fri, 02 May 2008 17:53:42 -0500, Jolly Roger <jollyroger.TakeThisOut@pobox.com>
wrote:

>1. The BASH profile file should be named .bash_profile - note the period
>character at the beginning. If the file is not named correctly, and does
>not exist in your home folder, BASH will not read it.
>
>2. Why are you trying to run a script?

To test to see if I had it with the right name and location.
 >> Stay informed about: cron on 10.5.2 server 

On Fri, 02 May 2008 17:53:42 -0500, Jolly Roger <jollyroger.DeleteThis@pobox.com>
wrote:

>1. The BASH profile file should be named .bash_profile - note the period
>character at the beginning. If the file is not named correctly, and does
>not exist in your home folder, BASH will not read it.

I tried to rename it from the finder, but failed. So I saved it from
TextWrangler, and it worked. So I will put in your code, test it, and
then copy it to my iPod for the other guy's computer.
 >> Stay informed about: cron on 10.5.2 server