similar to: Unknown socket option TCP_NODELAY

Hello, I found the folloing message in log.smbd [2001/04/18 13:00:41, 0] lib/util_sock.c:set_socket_options(165) Failed to set socket option SO_KEEPALIVE (Error Bad file number) [2001/04/18 13:00:41, 0] lib/util_sock.c:set_socket_options(165) Failed to set socket option TCP_NODELAY (Error Socket operation on non-socket) so I searched TCP_NODELAY in the INCLUDEFILES: (/usr/include/sys) >

We get the warning above whenever we use a ProxyCommand. We _know_ it's a pipe, so we can't use sockopts on it. So we shouldn't bitch about it. This breaks all kinds of things which use SSH transparently; including pine, which really wants the first thing it receives from an IMAP server to be a valid imap greeting... which $subject is not. $ ssh -o "proxycommand sh -c '(

Hi, I have a LDAP backend for my Samba 3.0.2, and everything seems to work except adding XP machines to the domain, and unix logins with a ldap client. Since this mail is very long, I have created a small index, so you don't get exhaustet in the middle of all the logs... ;) 1. LDAP user-creation 2. Group info 3. pam/nss info 4. smb.conf [global] 5. Log from trying to add machine to

I am trying very hard to get Samba working on my RedHat 5.1 system. I can't get past the 7th test in the Diagnosis.txt. On my Windows95 computer if I type 'net view \\MONSTER1' at a DOS prompt it returns an error: Error 54: The network is currently busy processing other requests or is out of resources. Try again later, or verify your network configuration to be sure that enough network

Hi, I run a Veritas cluster server with two different samba's 2.0.7 compiled with SUNWspro 4.0 (gcc 2.95 leads to the same results) on Solaris 7 UltraSPARC 60 server. One compiled with --prefix=/opt/samba-test the other with --prefix=/opt/samba-eng. To avoid using 127.0.0.1 or 0.0.0.0 when both smbd's running on the same cluster host I set this in both smbd.conf

https://bugzilla.mindrot.org/show_bug.cgi?id=2124 Bug ID: 2124 Summary: TCP_NODELAY not set by sshd for non-interactive non-exec sessions Product: Portable OpenSSH Version: -current Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 Component: sshd

smbclient is broken if TCP_NODELAY is enabled. I am running FreeBSD 2.2.7 Stable. 1. Enable socket options = TCP_NODELAY 2. Run smbclient to access a share on a Win95 box 3. Turn 'recurse' on 4. cd to a directory that contains one directory and no files 5. Do a dir 6. The files which live in the directory below the default directory will not be seen. 7. Eliminate TCP_NODELAY and they

Michael, With regard to your comment below: > As a streaming server, it's fairly crucial for icecast to send out > data with as low a delay as possible (many clients don't care, but > some do). That's why we use TCP_NODELAY - we actually WANT to send out > data as soon as we can. Can you explain how some clients depend on a low delay when receiving data from icecast? How

http://bugzilla.mindrot.org/show_bug.cgi?id=556 Summary: TCP_NODELAY not set completely for port forwarding Product: Portable OpenSSH Version: -current Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: openssh-unix-dev at mindrot.org

Hello SSH developers, I am sorry if this is not really a bug, and I am missing something, but I am running into an issue with port forwarding in SSH. I am using 3.4p1 of SSH on both sides. I am running the ssh daemon on a Slackware Linux 8.0 machine, and the ssh client is running in Cywgin version 1.3.13. The ssh client is creating about 7 port forwards in a mix of local and remote forwarding

Hi Henri and others, Very interesting post about TCP_CORK. I would be very interested in having it applied in the next version of Icecast. I'm using Icecast in a somewhat narrowcasting setup with large numbers of sources (> 100) and between 5 and 50 listeners per source. All streaming is done at low bitrates (16 - 24 kbit/sec) and listeners use embedded devices connected by 56k modems. It

I ran into the following problem the first time I used OpenSSH_3.6.1p2 on Solaris 8 (sparc, 32-bit): $ ssh kiwi Enter passphrase for RSA key '/net/sic/export/ford/home/eggert/.ssh/identity': getsockopt TCP_NODELAY: Socket operation on non-socket Last login: Sat May 10 14:27:01 2003 from ip-66-80-53-59.d Sun Microsystems Inc. SunOS 5.8 Generic Patch October 2001

Hello, >From smb.conf man page: "You may find that on some systems Samba will say "Unknown socket option" when you supply an option. This means you either incorrectly typed it or you need to add an include file to includes.h for your OS. If the latter is the case please send the patch to samba@samba.org <URL:mailto:samba@samba.org>." I'm exactly in that

I am seeing the following errors under Samba 2.0.6/Solarisy 7. I saw discussions of this on the Samba list but couldn't find any resolution. I saw the following message from Jeremy Allison > Message-ID: <387B949C.B499EC9C@valinux.com> > Date: Tue, 11 Jan 2000 12:37:48 -0800 > From: Jeremy Allison <jeremy@valinux.com> > Subject: Re: Error when

Hi, Why not turn off TCP_NODELAY in OpenSSH, atleast in the server->client direction? If a user is doing 'ls -l' over an Internet link that has some latency, he/she is flooded with a burst of small packets that can cause congestion and packet loss. Quite many people have been noticing this behaviour when doing ls -l resulting in <output> <delay> <output>

So far, bugs 2072 and 2140 have reported this condition. I was wondering if there was any movement on it. I know Richard Allen, author of 2140 and apparently the patch to bug 1065, had said he'd do some work on it. My "fix" for now has been ripping the #ifdef's out of config.h, but I still get a lot of complaints in the system log files about TCP_NODELAY, et. al: [2005/01/14

Hi, everyone. I originally sent this to the cifs-vfs mailing list, but upon reading the descriptions of the lists, I think that might have been the wrong place to ask. My apologies for the repeat. I hope I got the right place this time. :) I've noticed that the cifs client for Linux is slow over gigabit ethernet. It seems to max out at about 10 megs/sec, while the drives can go a lot

> > p.s. For an in depth analysis of TCP_CORK read Christiopher Baus' excelent > article: http://www.baus.net/on-tcp_cork Thanks for this pointer. I'd been meaning to reply on this thread, but hadn't got around to it, primarily because I didn't really understand TCP_CORK (the linux manpage is, as usual, fairly unclear on what exactly it does). Now I understand! > >

In certain situations sftp download speed can be much less than that of scp. After many days of trying to find the cause finally I found it to be the tcp nagle algorithm, which if turned off with TCP_NODELAY eliminates the problem. Now I see it being discussed back in 2002, but it still unresolved in openssh-4.2 :( Simple solution would be to add a NoDelay option to ssh which sftp would set.

I know that there was a discussion on this about a year back, and there is a bug 556 this week that mentions TCP_NODELAY. However, when I use ssh through a pipe (e.g., to tunnel through an HTTP proxy using CONNECT) I see: getsockopt TCP_NODELAY: Socket operation on non-socket How do I tell which end is generating this (I'm assuming the local side, which is running through the pipe). Also,