Path: utzoo!attcan!uunet!husc6!rutgers!cmcl2!phri!roy
From: roy@phri.UUCP (Roy Smith)
Newsgroups: comp.protocols.appletalk
Subject: Re: Problems installing lwsrv from CAP
Summary: It's mostly working now.
Keywords: lwsrv atis CAP spool
Message-ID: <3467@phri.UUCP>
Date: 7 Sep 88 21:24:04 GMT
References: <3455@phri.UUCP>
Reply-To: roy@phri.UUCP (Roy Smith)
Organization: Public Health Research Inst. (NY, NY)
Lines: 37


	In article <3455@phri.UUCP> sim@phri.UUCP (Kristian Simsarian)
writes about some problems we've been having getting lwsrv running.  Well,
we've got most of the problems solved now.

	Several people pointed out that we might be having a problem with
broadcasts.  Turns out that was the case.  Pretty much in desperation I
went at our atalkatab (which I consider to be largely black magic).  I
changed:

55.1  N1              128.122.136.0           PHRI-AT # PHRI AppleTalk

to:

55.1  H               128.122.136.150         PHRI-AT # PHRI AppleTalk

which seems to have solved the broadcast problem.

	Next we discovered a bug in lwsrv.  The last thing lwsrv does is
something like:

    sprintf(buf,"/usr/ucb/lpr -P%s %s %s -J 'MacUser: %s' %s\n",
	    unixpname,rflag ? "" : "-r",hflag ? "" : "-h", username,tname);

    system(buf);

	Note that the exit status of system isn't checked.  We were testing
lwsrv by printing from a machine called "Lizardi's Mac-II".  Of course, the
apostrophie (or single-quote, if you prefer) in the username makes the
system() fail.  Lwsrv really should check for things like that or just do a
fork/exec itself instead of system.  At the very least, it should check for
an error return from system().
-- 
Roy Smith, System Administrator
Public Health Research Institute
{allegra,philabs,cmcl2,rutgers}!phri!roy -or- phri!roy@uunet.uu.net
"The connector is the network"