9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jonathan Sergent <sergent@IO.COM>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Mial on cpu/auth server
Date: Mon,  4 Jun 2001 10:17:43 -0700	[thread overview]
Message-ID: <20010604171739.IVMO8623.femail1.sdc1.sfba.home.com@localhost> (raw)
In-Reply-To: <Pine.LNX.4.30.0106041230570.22138-100000@pali.cps.cmich.edu>


On Monday, June 4, 2001, at 09:33 AM, Ish Rattan wrote:

> I see the follwing messages in /sys/log/cron
>
> host Jun 4 06:52:04 upas: key not found
>
> similar message generated every 10 minutes. What key is it referring to?

The one for upas.  auth/changeuser upas to give it a key so that cron 
can authenticate as upas.  cron must run only on your auth server so 
that it can authenticate as the right user.  It does an rx to the target 
host to run the command.


  reply	other threads:[~2001-06-04 17:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-04 16:33 Ish Rattan
2001-06-04 17:17 ` Jonathan Sergent [this message]
2001-06-04 18:24   ` [9fans] Mail " Ish Rattan
2001-06-05  8:26     ` Alexander Povolotsky
2001-06-04 17:18 [9fans] Mial " anothy

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=20010604171739.IVMO8623.femail1.sdc1.sfba.home.com@localhost \
    --to=sergent@io.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).