9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: postmaster@ncrcae.ColumbiaSC.NCR.COM postmaster@ncrcae.ColumbiaSC.NCR.COM
Subject: SMTP mail warning
Date: Mon, 11 Mar 1996 01:40:02 -0500	[thread overview]
Message-ID: <19960311064002.vwhL5rcZnPbAvOYg8HcHBWNe5EAcMK9Y90UYC7jInbM@z> (raw)

  ---------- diagnosis ----------
SMTP diagnosis, WWIS Version 3.09 :
 

Not-Delivered-To: bharat!@bharat:karth@eggshel2 
	Due to: Message Transfer Agent Congestion
	(Cannot reach host. Delivery attempts will continue.)

  --------- unsent mail ---------
Received: by ncrcae.ColumbiaSC.NCR.COM; 9 Mar 96 16:55:26 EST
From: 9fans@cse.psu.edu
Received: from cse.psu.edu by casey.ColumbiaSC.NCR.COM; Sat,  9 Mar 96 16:53 EST
Received: from ncrgw1.UUCP (ncrgw1@localhost) by ncrhub4.attgis.com (8.7.3/8.7.3) with UUCP id QAA00647 for casey.columbiasc.ncr.com!karth; Sat, 9 Mar 1996 16:53:39 -0500 (EST)
Received: by ncrgw1.ATTGIS.COM; 9 Mar 96 16:53:28 EST
Received: by colossus.cse.psu.edu id <78360>; Sat, 9 Mar 1996 16:28:17 -0500
Received: from babbitt.bernstein.com ([206.20.83.129]) by colossus.cse.psu.edu with SMTP id <78359>; Sat, 9 Mar 1996 16:28:01 -0500
Received: (from triemer@localhost) by babbitt.bernstein.com (8.6.12/8.6.11) id QAA01519; Sat, 9 Mar 1996 16:34:39 -0500
Date: Sat, 9 Mar 1996 16:34:38 -0500
>From: babbitt.bernstein.com!triemer (Thomas Riemer)
To: cse.psu.edu!9fans (9fans)
Message-ID: <Pine.LNX.3.91.960309155859.1509A-100000@babbitt>
MIME-Version: 1.0
Content-Length: 1225
Content-Type: TEXT/PLAIN; charset=US-ASCII
Auto-Forwarded-From: casey!karth
Auto-Forward-Count: 1
Sender: owner-9fans@cse.psu.edu
Precedence: bulk
Reply-To: 9fans@cse.psu.edu

I've finally gotten through the majority of installation hurdles
and gotten a machine up and running... 

So here is the list of neophyte questions that I have:
1. Where is the equivalent of the "rc" files... i.e. where do I put
stuff so that things like "listen" get run automatically when the machine
boots.

2. I set up dns by running ndb/dns - this seemed to give me some 
form of nameservice.  If I understand the manuals correctly, this starts
up a domain name server on the machine.   Is there an equivalent to 
the /etc/resolv.conf idea of just specifying a domain server without
running a local name server?  BTW, the way the nameserver is running
currently it only seems to resolve fully qualified names...I presume
this is because it doesn't know what domain it is in... 
cat /dev/hostdomain produces nothing... how do I tell it what domain it
is in?  presumeably its in /lib/ndb/local. 
 

3. How do I "disable anonymous access"... The FAQ points to the -N
option in aux/telnetd... but where does one specify this -N?  (I just
answered this myself -despite the FAQ being vague... in /bin/service)

4. Who maintains the FAQ?

-Tom



---- Where theory and reality meet. 
---- Thomas Riemer, triemer@wesleyan.edu








             reply	other threads:[~1996-03-11  6:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-03-11  6:40 postmaster [this message]
1996-03-11  6:40 postmaster

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=19960311064002.vwhL5rcZnPbAvOYg8HcHBWNe5EAcMK9Y90UYC7jInbM@z \
    --to=postmaster@ncrcae.columbiasc.ncr.com \
    /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).