Em 13-01-2014 15:16, Armin K. escreveu:
> On 01/13/2014 07:12 PM, Bruce Dubbs wrote:
>> Armin K. wrote:
>>>
>>> Since you decided to put it in /sbin which isn't and shouldn't be in
>>> normal user path, it should be only run as root because of that.
>>>
>>> On the other hand, I can perfectly run it as normal user. It might just
>>> print a warning though, it isn't anything critical if it can't open
>>> /dev/kmem. That shouldn't be something user should be able to read anyways.
>>
>> I didn't decide, I suggested. Fernando is doing the page.
>>
>> If it prints a warning, it still runs, but what information is it
>> omitting from the output? I don't know without digging, but the
>> developer does recommend install using suid.
>>
>> If we do set the program suid, perhaps /bin would be better. For my
>> system, I do have /sbin in my path as a regular user, but that's
>> basically for development purposes.
>>
>> Just checking, I see /sbin/mount.nfs is suid. Also I have
>> /usr/sbin/vmware-authd as suid, but of course that's a proprietary
>> program that I was using to benchmark qemu against.
>>
>> -- Bruce
>>
>>
>
> I don't recall seeing a warning when I just ran "lsof", neither a
> reference to /dev/kmem. And again, looking at other distributions, none
> seem to have the executable installed as suid root.
>
I have tried both ways, no difference for me.
Using now:
install -v -m0755 lsof /usr/bin &&
install -v lsof.8 /usr/share/man/man8
I get a warning, always that, only that:
lsof: WARNING: can't stat() fuse.gvfs-fuse-daemon file system
/home/fernando/.gvfs
independent of suid root or not.
But have not yet read anything about it than this discussion here.
--
[]s,
Fernando
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
