HDTenEightyP/NetNews huggingface dataset:
From: QQ11@LIVERPOOL.AC.UK (Alan Thew)
Newsgroups: comp.protocols.nfs,comp.mail.elm,comp.sys.sun.admin
Subject: Re: Frequency of NFS lock problems w/ NFS mounted mail spool
Date: 4 Sep 92 13:59:02 GMT
 <vanepp.715392389@sfu.ca>
Organization: University of Liverpool

In article <vanepp.715392389@sfu.ca>, vanepp@fraser.sfu.ca (Peter Van Epp) says:
....
>>For several years, I have run small networks with /var/spool/mail
>>NFS-mounted from a single server to a bunch of workstations.  I have
>>yet to have a problem doing this.  Most of these machines have been
>>Sun's running a recent version of SunOS.
>
>>However, as I understand it, due to various bugs in various vendors'
>>rpc.lockds, this is running the risk of getting one's mailbox
>>thoroughly hosed if more than one process tries to write the mailbox
>>at once.
....
>>I'd be curious to know how many folks have actually had this kind of
>>problem -- if it turns out to be very few, NFS seems like it would be
>>worth the convenience.  Specific experience about the reliability of
>>the SunOS and Ultrix lockd's would also be interesting.
>
>>Also, where do the Elm lockfiles fit into all this?  Would they
>>prevent this problem (if everyone were to use Elm, that is), or do
>>they merely keep multiple copies of Elm from manipulating the same
>>mailbox simultaneously.
....
>
>As I recall (it has been about a year since I was through this) Elm uses
>flock()not lockf(), so NFS locking isn't a problem (nor possible for that     r
>matter since
>flock() won't work on an NFS file), what does the locking is the .lock file   t
>that
>Sun Sendmail creates in the mail spool directory. We have some 10,000 or so
>active users from 6 servers all accessing a mail spool NFS mounted on an
>Auspex
>without any problem. Again as memory serves, Elm is prepared to use the .lock
>file if asked to.
>
[ sorry for including so much quoted stuff but it all seemed relevant, I have
  also reduced the number of newsgroups ]

According to elm's config.h, the default is to use flock() and also .lock
files. So if I cannot trust rpc.lockd, then my MTA must use .lock files as
well and have a common lock directory with elm. The comments in config.h
are not clear whether this is /usr/spool/locks or /usr/spool/uucp...
(the defaults are based on Elm's Configure defaults).

Thanks for any futher input.

      Alan Thew : Computing Services Department, The University of Liverpool
Internet/Bitnet : qq11@liverpool.ac.uk       UUCP :  ....!mcsun!uknet!liv!qq11
          Voice :  +44 51 794 3735            Fax :  +44 51 794 3759
Newsgroups: comp.protocols.nfs
From: dte@cs.rit.edu (Dave Emlen)
Subject: PC-NFS w/ Windows problem
Followup-To: comp.protocols.nfs
Organization: Rochester Institute of Technology
Date: Thu, 3 Sep 1992 17:29:29 GMT


I'm trying to install PC-NFS (4.0a) on an AT&T 6386 w/ DOS 5.0 & Windows
3.1.  
It works fine in DOS, but when I go into Windows nothing works.  It doesn't
crash -- it just acts as if I'm not connected to the network at all.  Then
when I exit Windows and go back to DOS, it continues not-working. 
Sometimes
even just starting up Windows and exiting back to DOS will cause PC-NFS
to fail.  Has anyone seen this before?

Also, since this will be in a lab when it's working, is there an easy way
to
set it up so that all a person has to do is type in his/her username & 
password and it will find out which server their home directory is on and
mount it automagically?

Thanks in advance for any help!

--
Dave Emlen
Computer Science & Information Technology
Rochester Institute of Technology
dte@cs.rit.edu
Xref: sparky comp.protocols.nfs:2161 comp.protocols.tcp-ip.ibmpc:4908 comp.unix.aix:9122
From: curt@ekhadafi.austin.ibm.com (Curt Finch 903 2F021 curt@aixwiz.austin.ibm.com 512-838-2806)
Newsgroups: comp.protocols.nfs,comp.protocols.tcp-ip.ibmpc,comp.unix.aix
Subject: Re: Help with /etc/printcap under AIX (3.1.x)
Keywords: AIX PC-NFS printcap
Date: 26 Aug 92 05:13:02 GMT
Organization: IBM AWD, Austin

acw@evolving.com (Andy White) writes:
>Help!  I'm trying to allow a PC running Beame & Whiteside's PC-NFS to map a
>LPT port to a postscript printer hanging off of an AIX 3.1 server, running the
>bwnfsd daemon compiled from Beame & Whiteside's source (v2.3.0).  I created 
...
>According to the RTF'ed Manual, I need to define an /etc/printcap file.  After 

there is no such thing as /etc/printcap on aix
sorry

the lpr command is supported, as is lprm and lpq (output is different than
the real lpq)  but they are just argument mappers which call the enq
command with the proper arguments.  they don't behave EXACTLY like the
real lpr/lprm/lpq in all respects.

read the docs on /etc/qconfig and enq and qdaemon.
it may be necessary to modify the B+W code to behave slightly differently
on aix but i suspect if you just define the printers using smit
most everything will work.

does B+W bwnfsd support the pcnfsd v2 protocol yet?
if so the job becomes harder, since status and cancel are now supported

used 2 b u could just print jobs, which is easier
-- 
curt@aixwiz.austin.ibm.com (Curt L. Finch) | AIX NFS/NIS Field Quality 
My views are unrelated to those of IBM     |        Austin, TX
  Social Security isn't a retirement plan.  It's middle class welfare.
Newsgroups: comp.protocols.nfs,comp.protocols.tcp-ip.ibmpc,comp.unix.aix
From: beame@maccs.dcss.mcmaster.ca (Carl Beame)
Subject: Re: Help with /etc/printcap under AIX (3.1.x)
Keywords: AIX PC-NFS printcap 
Organization: McMaster University, Hamilton, Ontario, Canada.
Date: Thu, 27 Aug 1992 02:50:06 GMT

In article <1992Aug24.215339.16291@evolving.com> acw@evolving.com (Andy White) writes:
>
>Help!  I'm trying to allow a PC running Beame & Whiteside's PC-NFS to map a
>LPT port to a postscript printer hanging off of an AIX 3.1 server, running the
>bwnfsd daemon compiled from Beame & Whiteside's source (v2.3.0).  I created 
>an entry for the PC in question under /etc/hosts and also /etc/hosts.lpd (per
>B&W's instructions, there are also entries for the local server in each); and
>I'm having no problems mounting filesystems to appropriate DOS drive letters.
>According to the RTF'ed Manual, I need to define an /etc/printcap file.  After 
>a little research into the Berkeley ways, I came up with the following printcap 
>entry:
>
># this is all of /etc/printcap...
>ps|lp|HP IIIsi Laserjet w/ PostScript|:\
>	:lp=:rm=shakespeare:rp=ps:sd=/usr/lpd/qdir:\
>	:lf=/dev/null:
>
>(Okay, I admit sending errors off to /dev/null is bad form, but this is a
>quick & dirty test.)  Alas, the thing doesn't work.  Has anyone slain this
>particular dragon?
>
>Many thanks in advance...
>

	The /etc/printcap file needed for bwnfsd, is ONLY used to determine
the available printers. The file is parsed when bwnfsd is started and NET
LINK attempts are checked against the printers listed in /etc/printcap.
The daemon only uses the name fields, thus a printcap file can look like:

ps|lp|HP IIIsi Laserjet w/ PostScript:

	BW-NFS should be able to link to printers "ps" or "lp". If you are
still having trouble, please send mail to tech@bws.com or call us at
(416) 765-0822.

Carl Beame
Beame & Whiteside Software Ltd.
tech@bws.com
From: blane@athena.cs.uga.edu (Kate Blane)
Newsgroups: comp.protocols.nfs
Subject: OS/2 v 2 and PC-NFS 3.5
Date: 26 Aug 92 13:20:02 GMT
Organization: University of Georgia, Athens

Please excuse this post if this question has already been answered.

Does anyone have experience with OS/2 v 2 and PC-NFS 3.5 and
are they compatible?

We are running OS/2 v 2 on a Gateway 363, 33 Mhz with a WD8003e
Plus network card, 12 MB memory. The drivers in config.sys load
correctly but the initialization of the network (nfsrun,prt)
fails. If executed from autoexec.bat, the error message is roughly
"No internal or external command found..". If executed from the command
line, the error message is "No numeric coprocessor found.."

Please email to me unless you feel this would be of general interest
to this newsgroup. Thanks.
-------------------------
Kate Blane                                kate@zookeeper.zoo.uga.edu
Zoology Dept. UGA
-- 
==============================================================================
Kate Blane            Zoology Dept.  UGA        kate@zookeeper.zoo.uga.edu 
==============================================================================
From: george@ucs.adelaide.edu.au (George Travan)
Newsgroups: comp.protocols.nfs
Subject: PCNFS and local printing
Date: 26 Aug 92 02:53:27 GMT
Organization: Information Technology Division, The University of Adelaide, AUSTRALIA


I have installed pcnfs4.0 on our pc network linked to our SUN IPX.
Remote printing to the Sparcprinter on the IPX works OK from the pc's,
even within MS windows applications, such as MSword etc.
My problem which I just noticed is that I can no longer print to a 
pc's local printer when NFS is installed. Even as the default printer 
though the control panel this doesnt work.

To print to the local printer I have to uninstall PCNFS
It says in the manual that PCnfs 'doesnt interfere with the operation 
of any printers attached to your PC'. But I cant see anything wrong
with the way I access the local printer from mswindows.
Anyone have any pointers??

/Geo
From: brian@aim.com (Brian Flock)
Newsgroups: comp.protocols.nfs
Subject: Re: Free NFS Response Time Measurement Software
Summary: SunOS 4.1 and later has < 100 microsecond NIT timing services accuracy
Date: 25 Aug 92 18:42:57 GMT
Distribution: usa
Organization: /usr/lib/news/organization

In article <1992Aug20.213642.11024@engage.pko.dec.com> wiryaman@riscee.pko.dec.com (Santa Wiryaman) writes:
>>
>>                    *************************************
>>                    FREE NFS SERVER RESPONSE TIME UTILITY
>>                    *************************************
>>
>I have been using tcpdump and awk scripts to reduce the log file.  Tcpdump
>also uses NIT on Suns or packet filter on BSD UNIX and ULTRIX, I used the
>packet filter interface.  What I found was insufficient using this tool was
>the 4 ms. clock resolution.  On a midrange NFS server an operation such as
>getattr could easily be serviced at <1 ms.  So for accuracy, a microsecond clock
>resolution was needed.  What is the clock resolution of the SPARC workstations?

SPARC workstations with SunOS 4.1 and later have better than 100 microsecond
timing services accuracy.  Van Jacobson's timing code was incorporated in
SunOS 4.1, providing high speed counters with a factor of 40 greater accuracy
over the previous 4 ms resolution.

An AIM Technology internal development project based on the same code as NFSRTM
has been able to consistently measure response times under 500 microseconds.

>Also, how does NFSRTM deals with timeout and retransmissions?

NFSRTM recognizes retransmissions, but doesn't report them. A follow-on, 
commerical product will report this and other information with a graphical
interface.

Brian Flock
Product Manager
AIM Technology
brian@aim.com
From: wagner@chepil.weru.ksu.edu (Larry Wagner)
Newsgroups: comp.protocols.nfs
Subject: Re: PC-NFS 4.0a w/ NDIS & PKTD
Date: 27 Aug 1992 16:28:48 GMT
Organization: Kansas State University
Distribution: world
NNTP-Posting-Host: chepil.weru.ksu.edu
Keywords: pcnfs 4.0a, ndis, pktd, drivers

hliao@zeus.calstatela.edu (Henry Liao) writes:

>A while back, someone mentioned that it's possible to run packet-based
>applications, ie NCSA Telnet, on top of PC-NFS 4.0a w/ NDIS drivers using
>some kind of NDIS<->PKTD driver.  Any idea.  

I don't know anything about NDIS drivers, but it is possible to do
what you want, PCNFS and packet driver apps together.  You need to
get the pktd.sys file to allow PCNFS to use a packet driver and
the pktmux package that allows "sharing" of the packet driver among
PCNFS and other packet driver apps like NCSA Telnet, etc.
Limitations of this approach are very well discussed in the pktmux
documentation.

We are currently configured to do so with Clarkson's telbin, tn3270, etc.
and still have full PCNFS capability.  So far it is working fine, especially
after we re-read the pktmux documentation and discovered what option
was required to get ftp transfers to work within telbin and tn3270.

Since someone is going to ask, here is where pktd.sys and pktmux can
be obtained from...

pktd.sys
--------
Well, it looks like Geoff Arnold posted the latest version of pktd.sys
to comp.protocols.tcp-ip.ibmpc awhile back.  At least that is where I
got it from.  Someone else may know of an ftp site for it.

pktmux package
--------------
Updates of the software may be file transferred from the binary
file PKTMUXxx EXE (xx being version number without a point -
currently 11) on the RAL IBM mainframe (UK.AC.RL.IB on JANET,
IB.RL.AC.UK on the Internet) disc PCSOFT 192.  TCP/IP users of
Anonymous FTP should CD to PCSOFT.192 and binary GET PKTMUXxx.EXE.
Executing the file will produce the program and documentation.

--
Larry E. Wagner                     | wagner@chepil.weru.ksu.edu
USDA-ARS Wind Erosion Research Unit | wagner@matt.ksu.ksu.edu
105B East Waters Hall, KSU          | phone: (913) 532-6807 
Manhattan, KS 66506                 | fax:   (913) 532-6528
From: lonewolf@muse.Corp.Sun.COM (Peter Pak)
Newsgroups: comp.protocols.nfs
Subject: Re: PCNFS and local printing
Date: 26 Aug 1992 18:50:46 GMT
Organization: Sun Microsystems, Inc.
Distribution: world
Reply-To: lonewolf@muse.Corp.Sun.COM
NNTP-Posting-Host: muse.corp.sun.com

Hi George,

The problem you describe is documented in the PC-NFS 4.0 Release Notes.
(i.e. C:\NFS\README.TXT).  I've included the relevant section below.

Regards,

-Peter

**MICROSOFT WINDOWS SUPPORT**


USE PRINT MANAGER TO CONTROL PRINTING 

When configuring Printers to be used with PC-NFS software, it is
recommended that you use the Print Manager. You can do so by selecting 
"Use Print Manager" in Control Panel. Print Manager correctly handles 
output redirection to a local or remote printer. If you have problems 
printing to a local printer (i.e., one attached to your machine), go 
to Print Manager and verify that "Print Net Jobs Direct" is disabled. 
In Windows 3.1, select "Options" and then select "Network Settings." 
In Windows 3.0, select "Options" and then select "Network."
From: sob@TMC.EDU (Stan Barber)
Newsgroups: comp.protocols.nfs
Subject: Microsoft C 7.0 and the Programmer's Toolkit 1.0/4.0 for PC-NFS
Date: 30 Aug 1992 22:08:27 GMT
Organization: Baylor College of Medicine, Houston, Tx

It appears that the new compiler from Microsoft (as well as the Windows SDK)
will work just fine with the Programmer's Toolkit Verson 4.0 and you can
continue to build DOS only applications with the 1.0 toolkit as well. 

The secret is to add the OLDNAMES library when you compile.


The updated version of the whois utility I wrote for PC-NFS is available via
anonymous ftp from bcm.tmc.edu in the /whois directory. [There is also
one for Lan WorkPlace for DOS as well.]

Geoff, when will the next release be out? And, are there any gotchas that I
have not found yet?


-- 
Stan           internet: sob@bcm.tmc.edu         Director, Networking 
Olan           uucp: rutgers!bcm!sob             and Systems Support
Barber         Opinions expressed are only mine. Baylor College of Medicine
From: geoff@tyger.Eng.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top)
Newsgroups: comp.protocols.nfs
Subject: Re: PC-NFS name mapping.
Date: 4 Sep 1992 19:33:51 GMT
Organization: SunSelect
NNTP-Posting-Host: tyger.east.sun.com

Quoth slang@waikato.ac.nz (in <1992Sep3.123948.10558@waikato.ac.nz>):
#In the case where you have a FAT partition on a server, and a DOS systems as a
#client, it seems stupid that you can't even access the files by their own name!
#
#Is there a way around this at all? Am I missing something?
#
#I'm not looking to turn off all Name mapping, but if we were given the option
#of specifying UPPERCASE filenames to be the default, and then lowercase would
#be mapped, then it would fix at least one _SIMPLE_ situation that we have here.

In the next version of PC-NFS (no dates, no promises :-) there will
be a way to disable name mapping on a per-mount basis. This is
primarily intended for accessing NFS-mounted CD ROMs which use FAT-style
names. If the name is not 8.3 shaped, results are unpredictable,
however.

Geoff

--
Geoff Arnold, PC-NFS architect, Sun Select. (geoff.arnold@East.Sun.COM)
-----------
News software that enforces a four-line .signature limit is responsible for
the fact that these postings just go on and on and on and seem to end in mid-
Newsgroups: comp.protocols.nfs
From: blu@uunet.uu.net!mercomp (Brian Utterback)
Subject: Is there an archive of this group?
Organization: Mercury Computer Systems
Date: Tue, 1 Sep 1992 16:52:08 GMT

We recently upgraded a number of our PC-NFS users to version 4.0 and
they are starting to see problems.  However, rather than trying to
re-invent the wheel, I was wondering if there was an archive of this
group that I could use to see if they have already been discussed.

Thanks.

Brian Utterback
Mercury Computer Systems.
blu@mc.com

Newsgroups: comp.protocols.nfs
From: act@softserver.canberra.edu.au (Cyclops)
Subject: Re: Patch to pcnfsd-92.08.21
Organization: University of Canberra
Date: Thu, 3 Sep 92 23:42:29 GMT

gnb@duke.bby.com.au (Gregory N. Bond) writes:

>(*) Geoff: Can you please pretty please use the comment field in the
>net printers output if it looks like an interesting string?  Please?
>You are welcome to include these patches in the next distribution,
>should you wish to!

The ideas great but one is loathe to end up non-standard.

Geoff(too) Your thoughts and intentions pls.
-- 
Renrut Werdna			Probable-Possible, my black hen,
				She lays eggs in the Relative When.
				She doesn't lay eggs in the Positive Now
act@ss.canberra.edu.au		Because she's unable to postulate how
Newsgroups: comp.protocols.nfs
From: tomiii@mtu.edu (Thomas Dwyer III)
Subject: Re: PC-NFS & NIS
Organization: Michigan Technological University
Date: Tue, 1 Sep 1992 06:00:29 GMT

rhoward@matd.gatech.edu (Robert L. Howard) writes:
>hanke@nessie.cs.id.ethz.ch (Norbert Hanke) writes:
>
>>On quirk remains, however: trying to NET USE $NISSERVER:$HOME fails with
>>the message
>>  NFS057F : $HOME may only be used if the network information service is up.
>
>Actually I think you can do a simple:
>
>NET USE $HOME		(leaving off the $NISSERVER)
>

Unfortunately this is only true if you have an entry in your auto.home
map for each user.  Ideally, NET.EXE would have some code to process
wildcard lines such as:

	*	&:/usr/local/homes

Or even better yet, NET.EXE should use the home directory information
it got from rpc.pcnfsd during the NET NAME command, which must have
already happened in order for $HOME to know who's home to get!


Cheers,
Tom.III
tomiii@mtu.edu
Newsgroups: comp.protocols.nfs
From: dbander@netcom.com (David B. Andersen)
Subject: PCNFS and symbolic links
Date: Tue, 01 Sep 92 07:35:24 GMT
Organization: Netcom - Online Communication Services (408 241-9760 guest)
Distribution: comp.protocols.nfs
Keywords: pcnfs symlinks

When oh when oh when will pcnfs be able to deal with symbolic links?
(Are you listening Geoff?)

It is very frustrating to have all of the files which are symbolic links
in a directory be missing when you "dir" or "ls" them on a PC.

I haven't been following this news group for a while, so maybe this has
come up before, but does anyone else out there need this feature?  If so,
please sound off so we can get some action (hopefully).



-- 
/------------------------------------------------------------------\
|     David B. Andersen             (dbander@netcom.com)           |
\------------------------------------------------------------------/
Newsgroups: comp.protocols.nfs
From: dbander@netcom.com (David B. Andersen)
Subject: Re: PCNFS and symbolic links
Date: Fri, 04 Sep 92 06:43:57 GMT
Organization: Netcom - Online Communication Services (408 241-9760 guest)
Distribution: comp.protocols.nfs
Keywords: pcnfs symlinks

In article <1992Sep3.210904.8297@twg.com> oldera@twg.com (Ed Alcoff -  Prod Mtg) writes:
>(Geoff) correct me if I'm wrong, but I believe that PC-NFS
>can handle symbolic links, and if they are absolute, then
>you use the "net join" program.

How about it Geoff, is there a way for PC-NFS to see symbolic links?
Whenever I do a DIR or even an ls in a mounted directory known to 
contain symbolic links, the symbolic links do not appear.

Am I missing something?

-- 
/------------------------------------------------------------------\
|     David B. Andersen             (dbander@netcom.com)           |
\------------------------------------------------------------------/
From: dgd@nantucket.West.Sun.COM (Dan Donovan - Sun San Francisco SE)
Newsgroups: comp.protocols.nfs
Subject: Re: pcnfsd for Next?
Date: 27 Aug 1992 16:08:40 GMT
Organization: Sun Microsystems, Inc.
Distribution: world
Reply-To: dgd@nantucket.West.Sun.COM
NNTP-Posting-Host: nantucket.west.sun.com

Anyone using NeXTs as PCNFS servers knows that NeXT's daemon is Version 1.  Those
who have tried to port the Version 2 daemon included with PCNFS 4.0(a) will note
that it assumes a POSIX compliant environment (which NS 2.1 is NOT).  I suggest
getting a copy of Geoff Arnold's .latest release (pcnfsd.92.08.21.tar.Z).  It took
me about 20 minutes to port to NS 2.1.  Here are the steps, once you have a copy.

1.  Change the makefile to indicate you're compiling for SunOS 4.0.3 and not 4.1.1.
2.  Comment out the "#include <malloc.h>" in pcnfsd_print.c and pcnfsd_test.c.
3.  Change the two lines containing the function call "strdup" (not my_strdup) in
    pcnfsd_print.c to call my_strdup.
4.  make

Read your PCNFS 4.0 manual carefully since the V2 daemon expects to be started by
inetd and now needs a configuration file (/etc/pcnfsd.conf) to function properly.

Testing I've done so far with Windows 3.1 indicates that all of the V2 rpc
mechanisms seem to work.

As usual, no warrantee and your mileage may vary.

Dan

(Standard disclaimer.......)
   
Newsgroups: comp.protocols.nfs
From: vjs@rhyolite.wpd.sgi.com (Vernon Schryver)
Subject: Re: NIS across gateways
Organization: Silicon Graphics, Inc.  Mountain View, CA
Date: Sat, 29 Aug 1992 17:16:12 GMT

In article <1992Aug27.155241.7020@awdprime.austin.ibm.com>, curt@ekhadafi.austin.ibm.com (Curt Finch 903 2F021 curt@aixwiz.austin.ibm.com 512-838-2806) writes:
> I have a customer who sent me the following question:
> 
> >Within in an "area" there may or may not be routers.  We are thinking of
> >proposing the following idea regarding NIS:
> 
> >Within an area, there is one NIS master.  All other servers are
> >designated as slaves.  This will get around the router problem.
> >However, we noted that slaves could not get new copies of the maps
> >unless they were bound to the master.  Ideally, we would like to
> >have each slave bound to itself.  This way if a server goes down,
> >we know that users on the surviving servers do not have to wait
> >until their server is rebound.  We are unsure of deciding how to
> >best design around these binding issues.
> 
> NIS can't bind through a gateway generally since broadcasting doesn't
> work.  What sort of strategy might work for this, here are two I thought
> of:
> 
> 1.  Leave the slave bound to itself.  You might try having the master
>     rsh to the slave and run a shell script which does the following
>     whenever it's time to yppush:
>         ypset master
>         get all the maps
>         ypset slave
> 
> 2.  Or you could try leaving the slave always bound to the master but
>     running a cron job which tries to figure out when the master dies
>     and at that time rebinds to the slave until the master comes back
>     using ypset.
> 
> Can anyone tell me these ideas are wrong, or think of some others?


How about using multicast and IGMP?

If your router does multicast, and you can change your portmapper
and client libraries to try multicast, then it works fine.

I think there is an officially registered class-D address for this purpose.
I think it is 224.0.2.2.


Vernon Schryver,  vjs@sgi.com
Newsgroups: comp.protocols.nfs