Bug 110165 - net/linux-nx-client: update to 2.1.0-17
Summary: net/linux-nx-client: update to 2.1.0-17
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Gabor Kovesdan
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-10 19:10 UTC by Eric P. Scott
Modified: 2007-03-21 09:42 UTC (History)
0 users

See Also:


Attachments
file.diff (1.18 KB, patch)
2007-03-10 19:10 UTC, Eric P. Scott
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Eric P. Scott 2007-03-10 19:10:04 UTC
1. Update to latest NoMachine client release
http://www.nomachine.com/news-read.php?idnews=191

2. Correct spelling of PORTREVISION


On FreeBSD 6.2, proxy sessions may fail with this diagnostic:

Error: Failed to set TCP_NODELAY flag on FD#9 to 1. Error is 22 'Invalid argument'.

The problem does not manifest on FreeBSD 4.11.  A similar issue
arose on Mac OS X 10.4, so it's almost certainly a FreeBSD
regression.  NoMachine patched the nxcomp sources to ignore
errors returned by setsockopt() on Apple builds; however, the
check is still performed on Linux.  The correct place to deal
with this is in the Linuxulator, since "we" are almost certainly
in the wrong on this one.

More investigation is needed.
Comment 1 Eric P. Scott 2007-03-13 06:38:40 UTC
Please refer to
PR kern/110249
for explanation of the TCP_NODELAY problem and a proposed fix.

While it would be possible to intercept this in the Linuxulator,
it's easier to deal with it in the kernel--especially since it's
been proven to affect native executables as well (under FreeBSD
6.0, 6.1, and 6.2).
Comment 2 Gabor Kovesdan freebsd_committer freebsd_triage 2007-03-14 12:32:16 UTC
Responsible Changed
From-To: freebsd-ports-bugs->gabor

Take.
Comment 3 Gabor Kovesdan freebsd_committer freebsd_triage 2007-03-19 19:18:27 UTC
Hello Eric,

what do you think, should I commit this one or wait until the mentioned 
kernel issue gets solved?

Cheers,
Gabor
Comment 4 Eric P. Scott 2007-03-21 00:21:21 UTC
Commit, because it applies equally to 2.1.0-11 and 2.1.0-17.
Comment 5 Gabor Kovesdan freebsd_committer freebsd_triage 2007-03-21 09:41:37 UTC
State Changed
From-To: open->closed

Committed, thanks! If you want to maintain this port, please drop a private 
mail to me.