Path: utzoo!attcan!uunet!prcrs!paul From: paul@prcrs.UUCP (Paul Hite) Newsgroups: comp.sys.hp Subject: Re: Modems Message-ID: <935@prcrs.UUCP> Date: 5 Jul 90 15:12:03 GMT References: <1990Jun13.153719.17110@groucho> <560012@hpqtdla.HP.COM> <1131@kcdev.UUCP> Organization: PRC Realty Systems, McLean, VA Lines: 31 In article <1131@kcdev.UUCP>, gentry@kcdev.UUCP (Art Gentry) writes: > I missed the original discussion, so this may have already been discussed, > but it sounds suspiciously like you have 'getty' instead of 'uugetty' > spawned on the port. getty does not know how to handle 2 way traffic > gracefully. > We had trouble getting two way traffic to work, so we contacted the Response Center. We were using uugetty, but they told us that uugetty is not intended for use with modems on HP-UX. This doesn't jive with what we know from other platforms, but we followed the advice anyway and we have two traffic working with just getty. The Response Center told us that uugetty is intended only for use with hard-wired links. We did not have a special file correctly set up and the Responce Center also found that. I suspect that once the special file was correct, we really could have gone back to uugetty on the modem port, but we want to do things HP's way. We asked for an explanation of how cu, uucp, and getty avoid colliding with each other. getty opens the callin special file and blocks waiting for carrier detect. If cu or getty want the port, they open the callout special file which doesn't block. They will cause cd to be raised, but getty's open will then fail because it wants exclusive access. cu and uucp (uucico) never interfer with each other because of lock files. Anyway, we are using getty on a two-way modem port and the Response Center did say that uugetty should not be used on a modem port. I would be interested in hearing a lab type confirm (or deny) that this is the official HP line. Paul Hite PRC Realty Systems McLean,Va uunet!prcrs!paul (703) 556-2243 DOS is a four letter word!