Xref: utzoo comp.lang.c:11721 comp.sys.att:3918 comp.unix.questions:8603 comp.unix.wizards:10271
Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-tis!ames!ncar!oddjob!gargoyle!att!chinet!les
From: les@chinet.chi.il.us (Leslie Mikesell)
Newsgroups: comp.lang.c,comp.sys.att,comp.unix.questions,comp.unix.wizards
Subject: Re: dial() function call
Message-ID: <6213@chinet.chi.il.us>
Date: 5 Aug 88 15:37:23 GMT
References: <28@attibr.UUCP>
Reply-To: les@chinet.chi.il.us (Leslie Mikesell)
Organization: Chinet - Public Access Unix
Lines: 17

In article <28@attibr.UUCP> vch@attibr.UUCP (Vincent C. Hatem) writes:
>Has anyone out there ever got the dial(3C) function call to work???
>
>I've got a 3B2/600 running SysVr3.1.1 here, which comes with HDB uucp.
>
>This crazy dial() call uses the old style uucp files, which I've re-created.
>(Why be consistant???)
>

Even if it did work it would also use the old-style uucp lock files
which would not be consistant with uucp and cu.  There should be something
to this effect in the release notes (i.e. "Oh, by the way, dial()
doesn't work").  I ran into the same problem several years ago and
got a working dial.o from the hot-line people.  Hard to believe that
AT&T still has not fixed this in the C library.  Well, maybe not so
hard to believe, just depressing....

Les Mikesell