From: presotto@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] cron
Date: Sat, 30 Dec 2000 11:12:21 -0500 [thread overview]
Message-ID: <20001230161222.D2623199F9@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 226 bytes --]
Cron needs to be able to see the key file system. Generally, this is only
available on the auth server. You could start up keyfs on another system,
though you should worry about what processes can get at the file system.
[-- Attachment #2: Type: message/rfc822, Size: 1404 bytes --]
From: William Staniewicz <wstan@localhostnl.demon.nl>
To: 9fans@cse.psu.edu
Subject: [9fans] cron
Date: Sat, 30 Dec 2000 16:16:26 -0500
Message-ID: <20001230151952.8AF2D199E6@mail.cse.psu.edu>
Can cron be run on a standalone system? The manual
says it can only run on an authentication server.
I notice when I try to use it, a reference to a "key" pops up at the time I set it to carry out the command, but
nothing else happens.
Bill
next reply other threads:[~2000-12-30 16:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 16:12 presotto [this message]
2000-12-30 16:40 Russ Cox
2000-12-31 0:11 ` arisawa
2000-12-30 21:16 William Staniewicz
2000-12-30 15:33 ` Boyd Roberts
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20001230161222.D2623199F9@mail.cse.psu.edu \
--to=presotto@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).