Path: utzoo!utgpu!attcan!uunet!convex!killer!ames!pasteur!ucbvax!decwrl!hplabs!hpl-opus!hpccc!hp-sde!hpfcdc!rml
From: rml@hpfcdc.HP.COM (Bob Lenk)
Newsgroups: comp.sys.hp
Subject: Re: strange failure of chown(2)
Message-ID: <5570054@hpfcdc.HP.COM>
Date: 27 Jul 88 22:19:41 GMT
References: <2136@mhres.mh.nl>
Organization: HP Ft. Collins, Co.
Lines: 21

By default HP-UX follows the System V semantics of allowing any user to
chown(2) any file (s)he owns.  However, this can be restricted with the
privileged group facility.  If your system is set up this way, you would
get the EPERM error as described (and as on a BSD or V7 system).  To check
what privileged groups are set up on your system, type:

	getprivgrp

The output in the default configuration is:

	global privileges: CHOWN 

If CHOWN does not appear in the output, the system permits only the
superuser to chown files (except that any process can change the group
of a file it owns to another group in its group list).  In this case you
could permit group "mail" to have chown privilege as well.  See
getprivgrp(1) and setprivgrp(1m).

		Bob Lenk
		{ihnp4, hplabs}!hpfcla!rml
		rml%hpfcla@hplabs.hp.com