the command above, and I can provide my current
list of packages if necessary.
Any advice or suggestions would be appreciated.
Dale Hagglund
- start: kdump output -
34453 python 1223164746.661828 CALL munmap(0x2aa0,0xc1000)
34453
> "Mel" == Mel <[EMAIL PROTECTED]> writes:
Mel> Can you change scheduler to ULE and rebuild kernel?
Mel> Or better yet, try 7.1-PRERELEASE, since it's good to know if
Mel> this bug persists with 7.1 being close to release.
I'll rebuild with ULE first, and let you and the list kn
[Mel, the last time I replied to your @rachie address, I got a bounce.
I'm still including it here on the CC list. Should I remove it and just
reply to you via this list? --rdh]
Diane, Mel, thanks for your suggestions so far.
Mel> If upgrading ports is a possible solution, then you have the
, tcp(4) still gives the exact same
call used by vncviewer in its SYNOPSIS section; ditto for udp(4).
Anyway, I guess the basic question is whether or not this change in
the semantics of socket(2) was intended. In either case, I can submit
an appropriate PR if that will
Dale Hagglund <[EMAIL PROTECTED]> writes:
> I upgraded from 4.8 to 4.9 and my install of net/vnc couldn't connect
> to a remote server any more. The connection is via an ssh tunnel, but
> I don't think that's relevant.
Famous last words.
ssh binds its tunne
