X-Spam-Check-By: sourceware.org
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Subject: RE: Updated: inetutils-1.3.2-34 [setsockopt TOS (ignored): Protocol not available]
Date: Fri, 13 Jan 2006 01:12:09 -0000
Message-ID: <7231C15EAC2F164CA6DC326D97493C8B013B898B@exchange35.fed.cclrc.ac.uk>
From: "Adye, TJ \(Tim\)" <T DOT J DOT Adye AT rl DOT ac DOT uk>
To: "The Cygwin Mailing List" <cygwin AT cygwin DOT com>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k0D1COOY032160

Hi Corinna,

Thanks for the inetutils update. The inetd -D option is particularly
welcome (so thanks also to Bryan Thrall).

Unfortunately the new version's ftp, rcp, and rlogin commands give an
annoying new warning when connecting, eg.

  ftp: setsockopt TOS (ignored): Protocol not available

Actually, I suspect this is due to being compiled against updated
headers, because I got the same when recompiling an earlier version of
inetutils. Perhaps the IP_TOS (or similar) definition was added (since
you built inetutils last), even though it doesn't seem to be implemented
in setsockopt (for my XP SP2 system).

I assume the messages can be ignored, but it would be good if they could
be supressed.

Thanks,
Tim.

> -----Original Message-----
> From: cygwin-announce-owner AT cygwin DOT com On Behalf Of Corinna Vinschen
> Sent: 11 January 2006 16:30
> To: cygann
> Subject: Updated: inetutils-1.3.2-34
> 
> I've updated the version of inetutils to 1.3.2-34.
> 
> Unfortunately I found that I had a longstanding build problem 
> on my local machine, which could result in stuff like rlogind 
> bombing with a segmentation violation and similar "funny" problems.
> 
> However, since a release without some interesting change is 
> too boring, here we go:
> 
> 
> Changes in 1.3.2-34:
> 
> - Forced rebuild to fix longstanding(?) local build problem.
> 
> - Change syslogd-config script to deal with existing syslog-ng
>   installation, in preparation of upcoming syslog-ng package.
> 
> 
> ==============================================================
> ===========
> 			  IMPORTANT NOTE:
> 
> - When updating inetutils, take care that syslogd.exe, inetd.exe and
>   subsequent processes don't run anymore.  Otherwise the update will
>   fail.
> 
> ==============================================================
> ===========

===========================  cut here  ==========================
 Tim Adye     T DOT J DOT Adye AT rl DOT ac DOT uk     http://hepunx.rl.ac.uk/~adye
 BaBar Group, Particle Physics Dept, Rutherford Appleton Lab, UK

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/