Undeliverable mail: SMTP delivery failure

Mon Feb 18 19:34:37 AEST 1991

Return-path: <postmaster at VAX1.Mankato.MSUS.EDU>
Date: Sun, 17 Feb 1991 05:34 CST
From: PMDF Mail Server <Postmaster at VAX1.Mankato.MSUS.EDU>
Subject: Undeliverable mail: SMTP delivery failure
To: "MSUS1::IN%\"UNIX-WIZARDS at BRL.MIL\""@VAX1.Mankato.MSUS.EDU
Message-id: <A1867D8000207A4C at VAX1.Mankato.MSUS.EDU>

The message could not be delivered to:

Addressee: BD6 at MKATT1.MANKATO.MSUS.EDU
Reason: Illegal host/domain name found.

----------------------------------------

Received: from DECNET-MAIL by VAX1.Mankato.MSUS.EDU with PMDF#10000; Sun, 17
 Feb 1991 05:34 CST
Date: Sun, 17 Feb 1991 05:34 CST
From: "MSUS1::IN%\"UNIX-WIZARDS at BRL.MIL\""@VAX1.Mankato.MSUS.EDU
Subject: UNIX-WIZARDS Digest  V12#021
To: BD6 at MKATT1.MANKATO.MSUS.EDU
Message-id: <A17DBBFBE020814B at VAX1.Mankato.MSUS.EDU>
X-VMS-To: "Brian D. Goecke" <bd6%MKVAX1.DECNET at MSUS1.BITNET>

Date: Sun, 17 Feb 91 05:44:59 EST
From: Mike Muuss The Moderator <Unix-Wizards-Request at BRL.MIL>
Subject: UNIX-WIZARDS Digest  V12#021
Sender: Unix-Wizards Mailing List <UNIX-WIZ at NDSUVM1.BITNET>
To: "Brian D. Goecke" <bd6%MKVAX1.DECNET at MSUS1.BITNET>
Reply-to: UNIX-WIZARDS at BRL.MIL
Message-id: <A14E6B8EA0007666 at MSUS1.MSUS.EDU>

UNIX-WIZARDS Digest          Sun, 17 Feb 1991              V12#021

Today's Topics:
                       Re: Unbuffered pipe(2)'s?
      Re: Wizard-level questions (go4th & thread your primitives)
             Re: Help!  There's a slash '/' in my filename.
                       Re: Slashes in filenames?
            POSIX orphaned process groups: automatic SIGCONT

-----------------------------------------------------------------

From: "Brandon S. Allbery KB8JRR" <allbery at ncoast.org>
Subject: Re: Unbuffered pipe(2)'s?
Date: 16 Feb 91 02:34:08 GMT
Followup-To: comp.unix.wizards
To:       unix-wizards at sem.brl.mil

As quoted from <1991Feb08.151307.3160 at convex.com> by tchrist at convex.COM (Tom
 Christiansen):
+---------------
| It seems inappropriate to use comp.unix.wizards as an AI interface to TFM.
+---------------

Your intelligence is artificial?  :-)

++Brandon
--
Me: Brandon S. Allbery			    VHF/UHF: KB8JRR on 220, 2m, 440
Internet: allbery at NCoast.ORG		    Packet: KB8JRR @ WA8BXN
America OnLine: KB8JRR			    AMPR: KB8JRR.AmPR.ORG [44.70.4.88]
uunet!usenet.ins.cwru.edu!ncoast!allbery    Delphi: ALLBERY

-----------------------------

From: "Brandon S. Allbery KB8JRR" <allbery at ncoast.org>
Subject: Re: Wizard-level questions (go4th & thread your primitives)
Date: 16 Feb 91 02:48:51 GMT
Followup-To: comp.unix.wizards
To:       unix-wizards at sem.brl.mil

As quoted from <19041 at rpp386.cactus.org> by jfh at rpp386.cactus.org (John F Haugh
 II):
+---------------
| In article <8433 at suns5.cel.co.uk> mjp at cel.co.uk (matthew pidd) writes:
| > I've been tempted to write a FORTH compiler in C (as in build interactive
| >versions and loadable binaries with preprocessing etc) but just haven't had
| >the inclination. Does anyone know of such a creature ... and would it be
| >worth crafting?
|
| Yes, there is a "cforth" in some archive or another.  I have the
| source stashed away here, but don't recall which newsgroup I picked
| it out of.
+---------------

TILE was posted to comp.lang.forth,alt.sources (and might have been sent to
comp.sources.unix; I don't rememeber it having been in .misc, but since I
don't have the index any more I can't check :-) at least twice (different
versions).

++Brandon
--
Me: Brandon S. Allbery			    VHF/UHF: KB8JRR on 220, 2m, 440
Internet: allbery at NCoast.ORG		    Packet: KB8JRR @ WA8BXN
America OnLine: KB8JRR			    AMPR: KB8JRR.AmPR.ORG [44.70.4.88]
uunet!usenet.ins.cwru.edu!ncoast!allbery    Delphi: ALLBERY

-----------------------------

From: Rich Rauscher <rauscher at remus.rutgers.edu>
Subject: Re: Help!  There's a slash '/' in my filename.
Date: 16 Feb 91 16:29:53 GMT
To:       unix-wizards at sem.brl.mil

>Maybe they didn't.  How bout this sceniero.

>person types:   foo/bar and hits return
>wanted to type: foo.bar and hit return

>look at your keyboard.  it is possible.

Yeh, it's possible to type this but in almost all versions
of Unix, you'll just get an error 'No such
file or directory' or something like it.  This will
happen whether you're in a shell or application.

-Rich
--
 -------------
rauscher at rutgers.edu                RPO 5997 PO 5063, New Brunswick, NJ 08903
rauscher at PISCES                          Shakespeare learns Discrete Math:
{backbone site}!rutgers!rauscher                (2B | not (2B)) <=> TRUE

-----------------------------

From: Doug Gwyn <gwyn at smoke.brl.mil>
Subject: Re: Help!  There's a slash '/' in my filename.
Date: 16 Feb 91 20:31:40 GMT
To:       unix-wizards at sem.brl.mil

In article <Feb.16.11.29.52.1991.575 at remus.rutgers.edu>
 rauscher at remus.rutgers.edu (Rich Rauscher) writes:
>Yeh, it's possible to type this but in almost all versions
>of Unix, you'll just get an error 'No such
>file or directory' or something like it.  This will
>happen whether you're in a shell or application.

Look, guys, if you feel obligated to drag this discussion out,
you should go back and check the posting that started it.  The
problem is not that a user DESIRED to have a pathname COMPONENT
with a slash embedded in it; the problem is that a deficient
implementation ALLOWED one to be created, but it was much more
difficult to fix the situation once it had occurred.  If you
don't by now know how this could have occurred, you should not
be prolonging the discussion.

-----------------------------

From: Robert Thurlow <thurlow at convex.com>
Subject: Re: Slashes in filenames?
Date: 17 Feb 91 02:01:13 GMT
Sender: news access account <news at convex.com>
Nntp-Posting-Host: dhostwo.convex.com
To:       unix-wizards at sem.brl.mil

In <26038 at adm.brl.mil> STEINKEL%CAR1 at leav-emh.army.mil writes:

>If the prohibition on slashes in filenames is enforced by the kernel, how
>the bleep does NFS get them in there?

The NFS server on BSD/Sun systems is implemented as a module that calls
virtual file system (VFS) operations directly; the VFS is a layer below
the system call interface.  Since many of the old, inviolable firewalls
are implemented at the system call level, they had to be duplicated in
the NFS server logic.  Sun's initial implementation didn't catch a
number of these, and neither Sun nor the industry as a whole has kept up
with closing them as soon as they were found.  The slash issue is old
news; other things like the server permitting mknod()s by non-root
users are still being found.  One of the things that makes it tougher
is the fact that Unix clients can't send you such a request, since they
still have the firewall in the syscall.

Rob T
--
Rob Thurlow, thurlow at convex.com
An employee and not a spokesman for Convex Computer Corp., Dallas, TX

-----------------------------

From: Tor Lillqvist <tml at tik.vtt.fi>
Subject: POSIX orphaned process groups: automatic SIGCONT
Date: 17 Feb 91 16:01:01 GMT
Sender: news at tik.vtt.fi
Followup-To: comp.sys.hp
To:       unix-wizards at sem.brl.mil

I earlier posted a question concerning a problem I had on HP-UX 7.0
with POSIX sessions and signals: A process (A) creates a new session
and process group by calling setsid(), forks, then the parent process
(A) exits and the child (B) forks (and execs new programs) a couple of
times.  Now I stop one of these new child processes (C), but as soon
as another child process (D) exits, the stopped process (C) magically
continues.

The (A) process (the process group leader) forks after setsid() so
that it won't by accident acquire a new controlling terminal.

Quotes from the HP-UX manual pages:

exit(2):
	If the exit of the calling process causes a process group to
	become orphaned, and if any member of the newly-orphaned
	process group is stopped, all processes in the newly-orphaned
	process group are sent SIGHUP and SIGCONT signals.

glossary(9): (This entry is only in the printed manual!)
	orphaned process group:  A process group in which the parent
	of every member is either itself a member of the group or is
	not a member of the group's session.

According to the reply I got, HP-UX checks in exit() if the process
belonged to an orphaned process group, and sends the SIGHUP and
SIGCONT signals, *even if it wasn't this exit that caused the process
group to become orphaned*.

So, I got around my problem by not exiting in (A), instead only waiting for
(B) to finish.  Additionally, (B) calls setpgid(0,0) so that it and
the children will be in their own, non-orphan, process group.  (It is
not an orphan process group because the parent of (B) is in another
process group in *the same session*.)

Whew... well at least now I think I understand the POSIX session and
process group concepts.
--
Tor Lillqvist,
working, but not speaking, for the Technical Research Centre of Finland

-----------------------------

End of UNIX-WIZARDS Digest
**************************