Path: utzoo!utgpu!watserv1!watmath!iuvax!ux1.cso.uiuc.edu!ux1.cso.uiuc.edu!uxa.cso.uiuc.edu!jpd00964 From: jpd00964@uxa.cso.uiuc.edu Newsgroups: comp.sys.next Subject: Re: Kermit for NeXT Message-ID: <118400009@uxa.cso.uiuc.edu> Date: 24 Feb 90 18:34:00 GMT References: <124@cavanasic.nsc.com> Lines: 29 Nf-ID: #R:cavanasic.nsc.com:124:uxa.cso.uiuc.edu:118400009:000:1339 Nf-From: uxa.cso.uiuc.edu!jpd00964 Feb 24 12:34:00 1990 >Whenever I run HitchHiker, the machine slows to a crawl as soon as I >try to open a port. If I type into the string gadget which specifies >an external terminal, it takes several minutes for the text to show up. >The load average rises by 4-5 units, but no extra processes are running. HitchHiker must be owned by root and have its suid bit set or it cannot open the serial ports. The effects you describe sounds like HH is not set up this way. Go to it's directory and type ls -lg HitchHiker1.1 You should see -rwsr-xr-x root wheel <> Hitch....... if there is no s, you need to type chmod u+s HitchHiker1.1 while root. if root does not own it, the command is chown root HitchHiker1.1 Appearently, on a lot of NeXT machines, the owner becomes me instead of root. I have found this out through people E-Mailing me, but I have no idea why the number for root would be different on different machines. >Are there any happy HitchHiker users out there? While some people have E-mailed me saying that HH is perfect except for one bug or something, nobody has purchased it yet, so I don't think there are. Oh well, so much for a low-end shareware market for the NeXT. I will continue to support it, but until at least one person purchases it, there will be no HH1.2 Michael Rutman jpd00964@uxa.cso.uiuc.edu #include