On 22/03/11 17:42, Ed Curtis wrote:
Maybe someone can help out with this. I have a bash script I run at 1am
every morning via an entry in cron.d. It records an echo in a file when
done so I can record it running. The trouble I'm having with it is that
it's recording that's it has completed about
on 13:42 Tue 22 Mar, Ed Curtis (e_cur...@homes2see.com) wrote:
> Maybe someone can help out with this. I have a bash script I run at
> 1am every morning via an entry in cron.d. It records an echo in a
> file when done so I can record it running. The trouble I'm having
> with it is that it's recordi
Maybe someone can help out with this. I have a bash script I run at 1am
every morning via an entry in cron.d. It records an echo in a file when
done so I can record it running. The trouble I'm having with it is that
it's recording that's it has completed about once a minute from the hour
starti
On Thu, Oct 12, 2006 at 01:47:16PM -0500, cothrige wrote:
> > nano is just another editor - not as powerful as emacs, but sufficient
> > for me editing my crontab etc.
>
> Isn't it also called pico? I recall using that once way back when and
> it was okay as I recall. But Jed has always been my
* Serban Udrea ([EMAIL PROTECTED]) wrote:
> Hello,
Howdy,
> I am on Slackware 10.1 box right now and the man page for crontab states
> that crontab -e will use /usr/bin/vi or VISUAL. It does not mention
> EDITOR. On this box if VISUAL is not set, vi is run. If I set VISUAL to
> something els
On Fri, Oct 13, 2006 at 07:36:53PM +0200, Serban Udrea wrote:
>
> Hello,
>
> I am on Slackware 10.1 box right now and the man page for crontab states
> that crontab -e will use /usr/bin/vi or VISUAL. It does not mention
> EDITOR. On this box if VISUAL is not set, vi is run. If I set VISUAL to
cothrige wrote:
* Johannes Wiedersich ([EMAIL PROTECTED]) wrote:
As said by michael in another reply, the alternatives are overriden by
EDITOR or VISUAL.
Yes, that would make sense, but I had unset these in trying to get vi
to work with crontab. I guess I had assumed that vi would be the
* Johannes Wiedersich ([EMAIL PROTECTED]) wrote:
>
> As said by michael in another reply, the alternatives are overriden by
> EDITOR or VISUAL.
Yes, that would make sense, but I had unset these in trying to get vi
to work with crontab. I guess I had assumed that vi would be the
standard editor
* michael ([EMAIL PROTECTED]) wrote:
[snip...]
> >
> > Okay, I think I figured it out. In typing this email I was going to
> > yank in the output of crontab -l as it is odd.
>
> hang on, I thought you said it had *nothing* before
Yes, that was my mistake as it looked like nothing. It was
cothrige wrote:
* Johannes Wiedersich ([EMAIL PROTECTED]) wrote:
Which editor are you using? Please do a
ll /etc/alternatives/editor
Oddly it says nano as well, but my EDITOR and VISUAL variables are
both set to emacs, which is that which I use generally. And that is
what was invoked with cr
On Thu, 2006-10-12 at 12:05 -0500, cothrige wrote:
> * Johannes Wiedersich ([EMAIL PROTECTED]) wrote:
> >
> > Which editor are you using? Please do a
> > ll /etc/alternatives/editor
>
> Oddly it says nano as well, but my EDITOR and VISUAL variables are
> both set to emacs, which is that which I
* Johannes Wiedersich ([EMAIL PROTECTED]) wrote:
>
> Which editor are you using? Please do a
> ll /etc/alternatives/editor
Oddly it says nano as well, but my EDITOR and VISUAL variables are
both set to emacs, which is that which I use generally. And that is
what was invoked with crontab -e both
On Thu, 2006-10-12 at 18:37 +0200, Johannes Wiedersich wrote:
> cothrige wrote:
> > I am a Debian newb, coming from Slackware, and am trying to set up a
> > cronjob as a user. In other systems all I did was crontab -e and then
> > added the job. After if I ran crontab -l it was listed right there
cothrige wrote:
I am a Debian newb, coming from Slackware, and am trying to set up a
cronjob as a user. In other systems all I did was crontab -e and then
added the job. After if I ran crontab -l it was listed right there
ready to go. However, this is not working in Debian. Cron is
installed
On Thu, 2006-10-12 at 10:58 -0500, cothrige wrote:
> I am a Debian newb, coming from Slackware, and am trying to set up a
> cronjob as a user. In other systems all I did was crontab -e and then
> added the job. After if I ran crontab -l it was listed right there
> ready to go. However, this is n
I am a Debian newb, coming from Slackware, and am trying to set up a
cronjob as a user. In other systems all I did was crontab -e and then
added the job. After if I ran crontab -l it was listed right there
ready to go. However, this is not working in Debian. Cron is
installed and running, but w
16 matches
Mail list logo