Pathworks for OSF V1.2 and NIS

[Usask.Ca]

> Hi,
>
> I'm having trouble runnning NIS (formerly "Yellow Pages"), on our
> Pathworks for OSF server. If the /etc/svc.conf file says to use NIS for
> password lookups (any order), Pathworks connections begin taking 5-10
> minutes, or even longer, to be established.
>
> We're using an internal DEC package called "Pathworks for OSF Version
> 1.2", which is a simple-minded port of Pathworks for Ultrix 4.2, to the
> Alpha OSF platform (translated from the MIPS binaries, in part). This
> package was loaned to us by our local DEC sales office until Pathworks 5
> comes out officially for OSF. It's part of the DEC program that used to
> be called "Assets" -- internal software that isn't released as a regular
> product, but can be made available to customers to solve specific
> problems. I understand DEC have been using this package internally.
>

Gee, we paid for our copy!

> We're running it on OSF 1.3A, and all of our client pc's use the DECnet
> transport.
>
> I attempted to setup this OSF Pathworks server as our NIS master server.
> So far, there are no other NIS servers or clients.
>
> Can anybody shed any light on this? I've searched the documentation, and
> all the various logs, and haven't found anything relevant.
>
> Has anybody succeeded in using NIS with Pathworks for Ultrix? Any quirks
> that might have moved over with this port?
>

This is a known problem that has been fixed... after several months of beating
on DEC I finally got a patched PW for OSF1 1.2 kit which appears to be an
mx port of PW for Ultrix 1.2k... it works. The fellow I was talking to who
finally came through for me was roh...@solvit.enet.dec.com.

By the way, (for those of you that care !-) PW for Ultrix 1.2e through 1.2j
had a variety of problems for those of us using NIS (yellow pages)...
particularly if you have groups which require multiple entries in the group
file. PW 1.2k fixes these problems.

> My current wild guess is that maybe the TCP/IP transport would work, and
> the problem is with the DECnet transport. I haven't had a chance to test
> this.
>

Never tried this but I kinda doubt if tcpip would help.

> Yes, I've left a message with our local DEC pathworks technical person,
> but she and our sales rep warned us when they loaned us the package that
> we were on our own, so I'm not counting on getting any help locally.
>
> By the way, except for this problem with NIS, we're very impressed with
> Pathworks on OSF. Performance is amazing, especially after spending years
> on overloaded VAX/VMS servers (we've got a DEC 3000/800s). We're eagerly
> awaiting the Pathworks version 5 release for OSF.
>

If my opinion holds any sway around here, we'll be migrating to NTAS and
WFWG.

> I'll summarize if I get enough replies to warrant it.
>
> --Phil
>
> // Phil Rand pr...@spu.edu
> // Computer & Information Systems (206) 281-2428
> // Seattle Pacific University, 3307 3rd Ave W, Seattle, WA 98119
> //
> // A lack of planning on MY part may INDEED constitute an emergency on
> // YOUR part. -- Unix system administrators' motto
>
--
Nathan Epp - Systems Programmer |e-mail: Natha...@Usask.Ca
Department of Computing Services | Voice: (306) 966-4859
University of Saskatchewan | FAX: (306) 966-4938