On Tue, Feb 06, 2001 at 07:11:31AM +0100, peter karlsson wrote: > > Packages should almost never call dpkg_statoverride themselves. > > Earlier, that meant that the setuid/setgid bits got cleared > automatically by some daemon, is that not true anymore? Also, since the > setgid/setuid bit isn't in the actual package in my case (it can't be - > the group isn't created until after the package is decompressed), I > *need* to set the permissions on the file each time. Excerpt from the man page of dpkg-statoverride: - This can be used to force programs that are normally setuid to be - install without a setuid flag, or only executable by a certain group. In other words, _dpkg_ will override the package's requested owner and mode info with whatever the user has required. No daemon is required. I'm not sure if dpkg applies statoverrides at unpack time or after scripts have run. If it's the former, you have a problem. If it's the latter, you don't. I'd ask the dpkg people. -- Taral <firstname.lastname@example.org> Please use PGP/GPG to send me mail. "Never ascribe to malice what can as easily be put down to stupidity."
Description: PGP signature