home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!sdd.hp.com!uakari.primate.wisc.edu!crdgw1!ge-dab!puma.ATL.GE.COM!gthaker
- From: gthaker@fergie.atl.ge.com (Gautam H Thaker)
- Newsgroups: comp.sys.isis
- Subject: problems with ISISV2.1 on IBM RS/6000 workstations.
- Message-ID: <1992Aug14.152930.5359@puma.ATL.GE.COM>
- Date: 14 Aug 92 15:29:30 GMT
- Sender: news@puma.ATL.GE.COM (USENET News System)
- Organization: GE Aerospace, Advanced Technology Labs
- Lines: 20
-
- We use ISISV3.0.x in most situations, but for various reasons we have to
- use ISISV2.1 on an IBM RS/6000 machine on one project. Things are not
- working quite right on this IBM machine. The symptom is that socket files
- created as /tmp/Clxyzq do not seem to get deleted when sockets are closed.
- This requires manual deleting of these files every time. This even happens
- after one uses the "cmd" program. Attempts to use the cmd program a 2nd
- time fail and another file with names such as "/tmp/Cl1234" is seen.
- Another anamoly is that in the name "/tmp/Cl<pid>" pid only shows up as
- four digit number even though the actual pid would be a 5 digit number.
- I looked at the code of ISISV2.1 where these files are created, but nothing
- there explains this 5 digit to 4 digit translation.
-
- Anyone experience anything like this on ISISV2.1 and IBM machines? Is there
- a fix? Is this an OS problem?
-
- Gautam H. Thaker (gthaker@atl.ge.com)
- GE Adv. Tech. Lab.; Route 38, MS 145-2; Moorestown, NJ 08057
- 609-866-6412 (fax x6397. Dialcom 8-777) 767-4396 (home)
- --
- Gautam H. Thaker
-