From: anothy@cosym.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Mial on cpu/auth server
Date: Mon, 4 Jun 2001 13:18:40 -0400 [thread overview]
Message-ID: <20010604171849.9C85C199D5@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 280 bytes --]
//host Jun 4 06:52:04 upas: key not found
it's complaining that it can't authenticate. this is most likely
because "upas" isn't a user in your auth database. either create
a user upas or move the entries in /cron/upas/cron to
whoever's the postmaster (what i did).
-α.
[-- Attachment #2: Type: message/rfc822, Size: 1420 bytes --]
From: Ish Rattan <ishwar@pali.cps.cmich.edu>
To: <9fans@cse.psu.edu>
Subject: [9fans] Mial on cpu/auth server
Date: Mon, 4 Jun 2001 12:33:50 -0400 (EDT)
Message-ID: <Pine.LNX.4.30.0106041230570.22138-100000@pali.cps.cmich.edu>
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?
- ishwar
next reply other threads:[~2001-06-04 17:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-04 17:18 anothy [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-04 16:33 Ish Rattan
2001-06-04 17:17 ` Jonathan Sergent
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=20010604171849.9C85C199D5@mail.cse.psu.edu \
--to=anothy@cosym.net \
--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).