Ahem...
Why did I use the -o option? No idea. I meant to use the -I option, like
this:
ipmitool -I lan -H 192.168.104.130 ...
"lan" is not a valid option for -o. Still, ipmitool shouldn't segfault
if an invalid option is given to -o. But as far as I'm concerned, this
bug could be downgraded. It'
On Mon, 2006-07-10 at 14:01 +0200, Petter Reinholdtsen wrote:
> Can you run 'valgrind ipmitool -o lan -H 192.168.104.130 chassis
> status' and tell me what kind of errors it reports?
Sure -- the result of valgrind is attached. Please do tell me if there
is anything else you'd like me to try!
Chee
[Fabian Fagerholm]
> I'm including an strace. The host being accessed is an amd64 machine,
> but ipmitool crashes in the same way on both i386 and amd64.
Can you run 'valgrind ipmitool -o lan -H 192.168.104.130 chassis
status' and tell me what kind of errors it reports?
Friendly,
--
Petter Rein
Package: ipmitool
Version: 1.8.7-2
Severity: normal
ipmitool segfaults when accessing an IPMI-enabled host over LAN:
ipmitool -o lan -H 192.168.104.130 chassis status
Password: xxx
Segmentation fault
I'm including an strace. The host being accessed is an amd64 machine,
but ipmitool crashe
4 matches
Mail list logo
