> The documentation for uid/gid taken together with that for > forceuid/forcegid is misleading: it says that if no uid= option is > given (resp. gid=) then the value defaults to 0 (resp. 0), and that > forceuid= (resp. forcegid=) always forces the value of the uid= (resp. > gid=) option. > > However, this is not quite true: if no uid= (resp. gid=) option is > given, then forceuid (resp. forcegid) has no effect. > > It would seem to me that the best fix for this is to fix the > implementation, as the documentation sounds quite sensible, but I > guess this is less likely. To fix the documentation, it should be > noted for forceuid (resp. forcegid) that an explicit uid= (resp. gid=) > option is required.
Can you still reproduce this with 2:4.9-1 from unstable? AFAICS forceuid should now work without uid option. Cheers Luk -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
