I'm sorry, I wasn't specific enough.
The square brackets were meant to indicate an optional argument, not to
be typed in on the command line.
If you are logged in as the user that the cron job should run as, all
you need to do is:
crontab -e
If, however, you are logged in as root, for exampl
Well, you have to be logged in to the computer that you want the cron job
to run on in order to use the crontab command.
On Fri, Sep 20, 2002 at 01:08:14PM -0400, ebinc wrote:
- Hi thanks
- I enter the information into the cron direct by crontab [-u user] -e then
- enter it via ssh?
- so I can d
There is a file that cron uses that lists all the cron jobs.
You shouldn't edit this file directly, but you should use the crontab
command to edit it.
So:
crontab [-u user] -l### will list the current cron jobs
crontab [-u user] -e### will drop you into an editor to edit the jo
Just a thought... if you can't telnet to the box -- are you sure that
telnetd is running and listening on the port you are expecting it to be?
kristina
On Fri, Sep 20, 2002 at 03:15:57PM +0100, [EMAIL PROTECTED] wrote:
- I'm new to Linux and firewalls, but have several years SunOS/Solaris
- ex
the {} is a placeholder for the pathname of each file found
for some reason, commands need to be ended with an escaped semicolon...
kristina
On Thu, Sep 19, 2002 at 10:10:45AM -0500, Steve Buehler wrote:
- Ok. I found another way of doing it. Since chown does not appear to work
- the way the
