On Sat, 22 May 2004, chip wrote:
> So, now I am trying to run -
> crontab crontab
> in my non-root user directory, as the non-root user, and it fails with this-
> "crontab: crontab: No such file or directory"
> I tried -
> crontab -u chip crontab -e(with and without the -e)
> also and it failed
chip wrote:
Thanks for all the help. I like the changes so far. What about
specifically mentioning in the Handbook chapter that when a user runs
the command
crontab crontab
the user should do this in their own home directory. My problem was I
ran it in the /etc directory, not knowing any better,
Thanks for all the help. I like the changes so far. What about
specifically mentioning in the Handbook chapter that when a user runs
the command
crontab crontab
the user should do this in their own home directory. My problem was I
ran it in the /etc directory, not knowing any better, probably be
David Fleck wrote:
If you already have a file written in the proper format, you can load it
as your crontab by specifying 'crontab {filename}'. (That's what section
6.6.1 in the handbook is trying to say. Unfortunately, it is not at all
clear on this.)
There was an outstanding PR on this ... I mad
On Fri, 21 May 2004, carvin5string wrote:
[...]
> It would be nice to see some info about the differance between the
> system and user crontabs and how to properly create and use a user
> crontab, as well as when/why one would want to use a user crontab.
I missed the earlier parts of this exchange
--- Bill Moran <[EMAIL PROTECTED]> wrote:
> What you did was install the system crontab as a user. Log in as the
> user you executed "crontab crontab" as, and enter "crontab -r". That
> will remove the crontab for that user.
>
> On a related note. I'm going to make some changes to that section
carvin5string wrote:
--- Bill Moran <[EMAIL PROTECTED]> wrote:
You've got a user's crontab created in the format of the system
crontab.
The system crontab has an extra field to designate the user under
which
the job should run. When this field is entered in a user's crontab,
cron interprets it as
On Thursday 20 May 2004 22:57, carvin5string wrote:
> --- Bill Moran <[EMAIL PROTECTED]> wrote:
> > You've got a user's crontab created in the format of the system
> > crontab.
> >
> > The system crontab has an extra field to designate the user under
> > which
> > the job should run. When this fie
--- Bill Moran <[EMAIL PROTECTED]> wrote:
> You've got a user's crontab created in the format of the system
> crontab.
>
> The system crontab has an extra field to designate the user under
> which
> the job should run. When this field is entered in a user's crontab,
> cron interprets it as the c
On Thursday 20 May 2004 17:47, Bill Moran wrote:
> carvin5string wrote:
> > I have a new server set up and running and am getting a slew of
> > messages from cron, like this -
> >
> > Subject: Cron <[EMAIL PROTECTED]> root /usr/libexec/atrun
> > Body: root: not found
> >
> > and
> >
> > Cron <[EMAI
carvin5string wrote:
I have a new server set up and running and am getting a slew of
messages from cron, like this -
Subject: Cron <[EMAIL PROTECTED]> root /usr/libexec/atrun
Body: root: not found
and
Cron <[EMAIL PROTECTED]> operator /usr/libexec/save-entropy
operator: not found
What's g
On Thursday 20 May 2004 09:14, carvin5string wrote:
> I have a new server set up and running and am getting a slew of
> messages from cron, like this -
>
> Subject: Cron <[EMAIL PROTECTED]> root /usr/libexec/atrun
> Body: root: not found
>
> and
>
> Cron <[EMAIL PROTECTED]> operator /usr/libexec/sa
12 matches
Mail list logo
