Can confirm that this is resolved in lucid.
With 2.6.32-37-generic install of fprobe via apt-get fails with
"Starting fprobe: bind(): Invalid argument"
With 2.6.32-38-generic install of fprobe via apt-get is successful "Starting
fprobe: fprobe"
fprobe is running and sending netflow.
--
You rec
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: fprobe (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/899806
Title:
fpro
This also affects SLES11 SP1.
I updated a massive amount of packages, and after reboot Oracle Direct NFS does
not work any more. With standard in-kernel NFS client, everything works.
With the hint that I can use fprobe to testing (thanks!) I managed to
narrow down the problem source to the kerne
version 1.1.7-2 having same bug.
Made strace:
zhmak@server13:~$ sudo strace fprobe -i br0 127.0.0.1:5557
execve("/usr/sbin/fprobe", ["fprobe", "-i", "br0", "127.0.0.1:5557"], [/* 16
vars */]) = 0
brk(0) = 0x8fae000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENO
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/899806
Title:
fprobe start fails with "bind(): Invalid argument"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source
