search for: nodelay

...9 clustr-06 ######################################## # RAID 1 # TRANSPORT-TYPE tcp ######################################## ######################################## volume clustr-03-1 type protocol/client option transport-type tcp option remote-host clustr-03 option transport.socket.nodelay on option transport.remote-port 6996 option remote-subvolume brick1 end-volume volume clustr-03-2 type protocol/client option transport-type tcp option remote-host clustr-03 option transport.socket.nodelay on option transport.remote-port 6996 option remote-subvolume...

Hello again! Since there was some resistance against adding TCP_NODELAY uncontionally, I've made another patch. The new patch contains the following: * Added a NoDelay yes/no (default no) config option to ssh and sshd * Added -oNoDelay=yes to the ssh command line for sftp. * Changed the sshd subsystem config option syntax from Subsystem name path to Subsy...

On Tue, Jun 23, 2020 at 5:17 PM Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > > On 23/06/2020 12:15 Joe Wong <joewong99 at gmail.com> wrote: > > > > > > Hello, I have added 'y' as nodelay in my passdb query and I see the > following in log: > > > > dovecot: imap-login: Debug: Ignoring unknown passdb extra field: nodelay > > > > does it mean this option is no longer supported in 2.3.10 ? > > > > - Joe > > > > It is supported in 2.3.1...

Hello, I have added 'y' as nodelay in my passdb query and I see the following in log: dovecot: imap-login: Debug: Ignoring unknown passdb extra field: nodelay does it mean this option is no longer supported in 2.3.10 ? - Joe -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dovecot.org/pi...

...ote: > > > > > On Tue, Jun 23, 2020 at 5:17 PM Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > > > > On 23/06/2020 12:15 Joe Wong <joewong99 at gmail.com> wrote: > > > > > > > > > Hello, I have added 'y' as nodelay in my passdb query and I see the following in log: > > > > > > dovecot: imap-login: Debug: Ignoring unknown passdb extra field: nodelay > > > > > > does it mean this option is no longer supported in 2.3.10 ? > > > > > > - Joe > >...

> On 23/06/2020 12:15 Joe Wong <joewong99 at gmail.com> wrote: > > > Hello, I have added 'y' as nodelay in my passdb query and I see the following in log: > > dovecot: imap-login: Debug: Ignoring unknown passdb extra field: nodelay > > does it mean this option is no longer supported in 2.3.10 ? > > - Joe > It is supported in 2.3.10. The extra field is ignored by imap-login pr...

http://bugzilla.mindrot.org/show_bug.cgi?id=594 Summary: SSH tries to set nodelay on non-sockets Product: Portable OpenSSH Version: -current Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: openssh-bugs at mindrot.org ReportedBy: ji...

...d-volume volume brickex type performance/io-threads option thread-count 4 subvolumes locks1 end-volume volume server-tcp type protocol/server option transport-type tcp option auth.addr.brickex.allow * option transport.socket.listen-port 6996 option transport.socket.nodelay on subvolumes brickex end-volume -------------- next part -------------- # file auto generated by /usr/local/bin/glusterfs-volgen (mount.vol) # Cmd line: # $ /usr/local/bin/glusterfs-volgen --name gfs 172.24.0.68:/ghostcache/home/hsawhney/gfs/ 172.24.0.222:/ghostcache/home/hsawhney/gfs/ # TRAN...

...hange permissions from windows.. In windows I can see that I'm a valid user for this folder (all permisssions) but I can't change permissions on this folder an also I can't add files or folders to it.... I only changed the samba entry in the pam.d folder: Auth required pam_winbind.so nodelay Account required pam_winbind.so nodelay Session required pam_winbind.so nodelay Password required pam_winbind.so nodelay - do I have to change some more of these files to get this working? Regards Dieter -----Urspr?ngliche Nachricht----- Von: Denis M.J. [mailto:m21@altern.org] Gesendet:...

...that would have its own delays, but there are no guarantees about this. If the old behavior is still wanted, it's possible to do nowadays even more generically with e.g.: passdb { driver = passwd-file args = username_format=%{rip} /etc/dovecot/passdb } /etc/dovecot/passdb: 127.0.0.1:::::::nodelay=yes 192.168.10.124:::::::nodelay=yes --- STOP --- Adding the passdb section and creating a passdb file with the respective ip addresses does not have any effect though. Login failures through the webmailer are still being delayed. "dovecot -n" shows that the new passdb section is loade...

In order to test my overlapping request path for sftp on another ssh server, I downloaded ssh2 version 3.1.0 from ssh.com. Having downloaded it, I decided to study the use of TCP_NODELAY in that implementation. Here's what I found: * Both ssh2 and sshd2 has a NoDelay config option which is false by default. * The ssh2 client does not enable or disable NoDelay because of a channel type (such as pty or X11). * The sftp2 client uses "-o NoDelay=yes" when starti...

This time the problem is that the ssh server only sets TCP_NODELAY for interactive (tty) sessions or if X11 forwarding is enabled. Neither of which are true for the use of the sftp subsystem. This hurts upload performance for sftp/sshfs. I'm not sure why this hasn't cropped up earlier. Were there any TCP_NODELAY related changes in the sshd code recentl...

...y I don't want to wait several minutes for the tests to finish. Setting the configuration variable auth_failure_delay to 0 worked fine in Dovecot 1.2, but since Debian updated to Dovecot 2.0 it no longer works. The tests take a very long time to run. I tried changing my passwd file to include nodelay=y, but this only works in a very limited way. For the set of tests which use the correct username, but an incorrect password, this successfully disables the failure delay. However, for the set of tests which use incorrect usernames (names not found in the user database or the password database, and...

> 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. Nagle is inherently unsuited for streams. NODELAY was (imho) ment for connections for which Nagle isn't sufficient and CORK is not an option, i.e. telnet. Sending the data as soon as you can might not be the way to go, since this ha...

...rt. It works as expected in that it returns the correct values and proxies to the correct backend. However it seems that TLS is no longer working and I get timeouts from the backends. Debug: client passdb out: OK 1 user=someuser at example.com proxy proxy_nopipelining=y host=backend1.example.com nodelay=y nologin starttls=no ssl=any-cert hostip=so.me.i.p pass=<hidden> results in: Sep 17 11:08:47 imapproxy1 dovecot: imap-login: Error: proxy(someuser at example.com): Login for so.me.i.p:993 timed out in state=/none (after 30 secs, local=lo.cal.i.p:60524): user=<someuser at example.com>,...

Hi, For the upcoming 2.3 development, I'd like to re-suggest this: It seems the use of login_trusted_networks is overloaded. Example: * It's used for indicating which hosts you trust to provide XCLIENT remote IP's. (like a proxy) * It's used for indicating from which hosts you trust logins enough to disable auth penalty. (like in a webmail) Often these two uses cases have a

...ovecot.passdb } socket listen { client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } mechanisms = plain login user = root count = 1 } dovecot.passdb: testuser1:::::::host=<internalip> port=143 nodelay=y nologin=y proxy=y testuser2:::::::host=<internalip> port=143 nodelay=y nologin=y proxy=y dovecot.log: dovecot: Oct 06 10:37:26 Info: Dovecot v1.1.7 starting up dovecot: Oct 06 10:37:26 Info: auth(default): passwd-file /etc/dovecot/dovecot.passdb: Read 2 users dovecot: Oct 06 10:37:27 In...

...sers,domainName=%d,o=domains,dc=example,dc=com scope = subtree deref = never user_filter = (&(mail=%u)(objectClass=mailUser)(accountStatus=active)(enabledService=mail)(enabledService=%Ls)) user_attrs = storageBaseDirectory=home,mailHost=host,=proxy=yes,=nologin=yes,=nodelay=yes pass_filter = (&(mail=%u)(objectClass=mailUser)(accountStatus=active)(enabledService=mail)(enabledService=%Ls)) pass_attrs = userPassword=password,mailHost=host,=proxy=yes,=nologin=yes,=nodelay=yes default_pass_scheme = CRYPT ### /var/log/mail/dovecot.info Nov 30 14:26:59 dougie...

Hi there, I just tried out OpenSSH3.0p1 running on Solaris 8 with PAM (--with-PAM). The problem was mentioned some time ago and is still there :-( When a password is expired you are prompted to change it now, enter your login password and after doing so you are instantly disconnected. I think this is a problem with PAM and not SSH, but how can I get a solution on this ? sshd is running without

...y with IFs to fake proxy_maybe and return the password as NULL and nologin as Y, but if it works that way couldn't it work with proxy_maybe? This works: password_query = \ SELECT NULL AS password, host, CONCAT(user,'@',domain) AS destuser \ 'Y' AS nologin, 'Y' AS nodelay, 'Y' AS proxy \ FROM accounts WHERE class='pop' AND domain='%d' This doesn't work if proxied and CRAM-MD5 auth: password_query = \ SELECT \ CONCAT(user,'@',domain) AS user, password, \ host, 'Y' AS proxy_maybe, \ target AS userdb_home,...