home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.unix.sysv386:13675 comp.unix.xenix.sco:2750
- Path: sparky!uunet!crdgw1!rdsunx.crd.ge.com!ariel!davidsen
- From: davidsen@ariel.crd.GE.COM (william E Davidsen)
- Newsgroups: comp.unix.sysv386,comp.unix.xenix.sco
- Subject: SCO support - a success story
- Message-ID: <1992Aug27.132540.8677@crd.ge.com>
- Date: 27 Aug 92 13:25:40 GMT
- Sender: usenet@crd.ge.com (Required for NNTP)
- Reply-To: davidsen@crd.ge.com (bill davidsen)
- Followup-To: poster
- Organization: GE Corporate R&D Center, Schenectady NY
- Lines: 28
- Nntp-Posting-Host: ariel.crd.ge.com
-
-
- Back in May I reported problems with Xenix cron dying after heavy use.
- I had reported it to SCO and they had no ready fix. Well SCO didn't quit
- on the problem, they first suggested workarounds, and then started
- sending me new binaries to try.
-
- Since the failures were after some days, and SCO didn't have a machine
- with the proper peripheral to run our code (a coal fired power plant),
- this whole process has been lengthly, not through lack of interest or
- effort on the part of SCO, but because it really slow to debug stuff by
- looking at dumps you get once a week.
-
- In the end, success! We have a version which seems totally stable and
- can get on with providing the electrons the net needs. Think of it, half
- the electrons in the message were provided by GE turbines and
- generators!
-
- I mention this because various vendors have been getting heat in
- several groups about support. Even though only one customer reported
- this problem, SCO stuck with and fixed it. Thanks folks!
-
- SCO says it will be fixed in the next release, so I guess that's a
- committment that there will /be/ a next release of Xenix, something I
- wouldn't have considered certain.
-
- --
- bill davidsen, GE Corp. R&D Center; Box 8; Schenectady NY 12345
- I admit that when I was in school I wrote COBOL. But I didn't compile.
-