On Mon, 16 Sep 1996, Dan Rosenblatt wrote: [snip] > The problem shows up when trying to send a fax (full server trace). > There are various 'chown' errors and then 'Operation not supported'. > Anyone have suggestions as to what might be going on. > The servers are started from root, and a ps shows that their uid > (effective?, real?) is uucp (aka fax). Could there be a problem > with switching uids back and forth between root to uucp/fax? > Could there be a problem with doing 'chown' to give away ownership? > [snip] > Sep 14 17:21:34 argon HylaFAX: /tmp/doc48.ps: chown: Invalid argument > Sep 14 17:21:34 argon HylaFAX: /tmp/doc48.ps: chown: Invalid argument > Sep 14 17:21:34 argon HylaFAX: <--- 150 FILE: /tmp/doc48.ps (Opening new data connection). > Sep 14 17:21:34 argon HylaFAX: <--- 226 Transfer complete (FILE: /tmp/doc48.ps). The problem is due to the HylaFAX using the default owner id (actually the gid) of [some-big-number]. SCO's chown actually seems to check this against something, and that's why it's complaining. The fix is to change the etc/hosts to have the default fax-user-id to some lower gid number. eg: 127.0.0.1:5:: # local access -- Jonathan Chen e-mail : firstname.lastname@example.org
This problem was fixed in v4.0pl1. HylaFAX now detects the maximum value for the GID during configuration.