Guy Harris
changed
bug 9516
| What |
Removed |
Added |
| Hardware |
x86
|
All
|
Comment # 10
on bug 9516
from Guy Harris
(In reply to comment #9)
> Filesystem 1K-blocks Used Available Use% Mounted on
> 10.118.213.156:/home/vishnu.bhatt
> 300648216 201159640 83970184 71% /home1/vishnu.bhatt
OK, that's NFS, and you can't set capability bits over NFS, as NFS has no
notion of capability bits for files.
I don't know what the right way is to construct a package that sets
capabilities on files if possible and doesn't give errors if it can't.
And part of the problem here is that Wireshark *will behave differently*
depending on whether the capabilities are set on dumpcap or not - it will be
able to capture without special privileges if they're set, but won't be able to
capture with special privileges if they're not.
I would try doing "make distclean" and then configuring with
--disable-setcap-install and --enable-setuid-install and building Wireshark and
the RPM; that might get rid of the setting of the capabilities and, instead,
make dumpcap set-UID, which is the best you can do with an NFS-mounted file
system.
Try that and see whether it works. If not, we might have to make the "build
the RPM" steps pay attention to those two configuration flags.
You are receiving this mail because:
- You are watching all bug changes.
