![]() |
And the prize goes to Jonathan Chen. He got me thinking. I remember we had this problem with SCO Open Server 5. I thought UnixWare 7 was UnixWare, but I keep forgetting there is way too much Open Server 5 code in there. (I just wish they wouldn't use the broken code) It turns out we need to set CONFIG_MAXGID=60000. I've included a patch that includes all the (curently known) changes to configure and config.site needed for UnixWare 7. I've also included a change to handle the runaway faxgetty problem in UnixWare 2.1.3 (CONFIG_OPENFIFO=O_RDWR) It still works with earlier versions of UnixWare. Enjoy. On Tue, 6 Oct 1998, Jonathan Chen wrote: > On Mon, 5 Oct 1998, Tim Rice wrote: > > > On Mon, 5 Oct 1998, kees wrote: > > > > > Hello, > > > I assume you checked owner/permissions of the directories in $FAXSPOOL > > > as well the same for the seqf files..... > > > Kees > > > > > > > Yes I did. But then I would expect an EPERM error on permissions problems > > not an EINVAL. > > > > Hmm, could this be due to a unexpectedly large gid on the current > process? ie, if you're running with a gid that the file-system doesn't > like it won't create a file with that gid hence the EINVAL error. > > [Reaching for answers...] > > Jonathan Chen > ---------------------------------------------------------------------- > "By the time they had diminished from 50 to 8, > the other dwarves began to suspect 'Hungry' ..." - Gary Larson > > -- Tim Rice Multitalents (707) 887-1469 (voice) tim@trr.metro.net Attachment Converted: "C:\PROGRAM FILES\EUDORA\Attach\uw71.pat"