similar to: inetd mode

Hello. I'm having the following problem with dovecot 1.0.12 and above, on a FreeBSD 7.0 system - I'm trying to run pop3-login from inetd and I keep getting this error after authentication: May 25 09:46:19 charlie dovecot: POP3(gelu): /libexec/ld-elf.so.1: environment corrupt; missing value for no-nuls oe-ns-eoh The problem persists if I uncomment the lines with no-nuls oe-ns-eoh in

On Thu, 2014-01-30 at 11:25 -0500, Dan Swartzendruber wrote: > Hopefully I'm not out to lunch here. I ported tftp-hpa to our proprietary > OS, VOS (at stratus.com). We've always runs the old legacy tftpd from > inetd, so I wanted to continue doing so with tftp-hpa. It seems to work > okay, but I noticed that the code in tftpd.c has a 'while (1)' loop that > has

> Correct. Like most UDP-based inetd services, tftpd is intended to be run in 'wait' mode. When the first request arrives, inetd starts the service but does not read the incoming packet (it can't, because it has no way to pass it along to the server). After that, inetd ignores that socket until the server exits. This isn't critical for tftp, but it does help to keep down the

On 01/30/2014 10:25 AM, Jeffrey Hutzelman wrote: > > Correct. Like most UDP-based inetd services, tftpd is intended to be > run in 'wait' mode. When the first request arrives, inetd starts the > service but does not read the incoming packet (it can't, because it has > no way to pass it along to the server). After that, inetd ignores that > socket until the server

Hi. -alpha2 broke the retr-byte-count field of the pop3_logout_format with the following change: -Added %R (reverse string) and %H (hash string) variable modifiers. %R as modifier conflicts on expand with %R as retr-byte-count in pop3_logout_format resulting in expanded strings like: top=0/0, retr=1/ del=0/1, size=431 seen in -alpha3 -alpha4 cvs as of 04.11.2005 FreeBSD 5.4-R, both i386

Dovecot 0.99.13. I've noticed that the condition client->secured = ssl || (IPADDR_IS_V4(ip) && strncmp(addr, "127.", 4) == 0) || (IPADDR_IS_V6(ip) && strcmp(addr, "::1") == 0); (in (imap-login|pop3-login)/client.c) isn't enough, at least not when running from inetd. The thing is that you will come across ::ffff:127.0.0.1, which is secure,

Hopefully I'm not out to lunch here. I ported tftp-hpa to our proprietary OS, VOS (at stratus.com). We've always runs the old legacy tftpd from inetd, so I wanted to continue doing so with tftp-hpa. It seems to work okay, but I noticed that the code in tftpd.c has a 'while (1)' loop that has this at the end: /* * Now that we have read the request packet from

Hi! When running dovecot from inetd (as per the instructions on http://wiki.dovecot.org/InetdInstall), imap-login and pop3-login thinks that TLS is enabled when in fact it isn't (we're connecting to port 110 and port 143, so the --ssl parameter isn't present). The reason for that is found in login-common/main.c:main(): > if (fd != -1) > (void)client_create(fd, &ip,

Hey.. I'm finding that I can force dovecot (setup in inetd mode) into a wedged state by spamming it with carrage returns. As I've not had enough time to familiarize myself with the code.. I thought I'd ping the list before 1.0 is christened. -Phil.

Hi, When running in inetd mode (-i), if stdin/stdout are not an IP socket, sshd will set PAM_RHOST to "UNKNOWN" which causes a reverse DNS lookup by pam that always fails because "UNKNOWN" cannot be resolved. I've posted a possible fix here: https://github.com/openssh/openssh-portable/pull/388 Cheers, Daan De Meyer

Hi. I don''t know if this one is known, but I can''t recall seeing anything about it. If it is old news I apologize. I discovered a bug in the inetd that comes with NetKit-B-0-08 and older. If a single SYN is sent to port 13 of the server, inetd will die of Broken Pipe: write(3, "Sun Jan 12 21:50:35 1997\r\n", 26) = -1 EPIPE (Broken pipe) --- SIGPIPE (Broken pipe) ---

When I ran /usr/local/sbin/dovecot, the variable login_log_format_elements from dovecot.conf was honored. Now when I run /usr/local/libexec/dovecot/imap-login from /etc/inetd.conf, it isn't. How do I get imap-login to write log lines that use login_log_format_elements for the format? This is dovecot-1.2.alpha3 soon to be alpha4. Thanks, Jonathan -------------- next part -------------- A

Environment: Solaris 2.5.1 Samba 1.9.18p3 We run samba from inetd (no special reason - just how its been done in the past). Then on one server we got masses of Samba daemons running (up to 40 as a time trying to run - load average 40+!), giving following complaints: Sep 28 14:39:06 zeus.brunel.ac.uk smbd[10728]: standard input is not a socket, a ssuming -D option Sep 28 14:39:06

I'm trying to start SAMBA from the inetd. I have added the port numbers to /etc/services: netbios-ns 137/udp netbios-ssn 139/tcp To my inetd.conf I have added: netbios-ssn stream tcp nowait root /usr/local/samba/bin/smbd netbios-ns dgram udp wait root /usr/local/samba/bin/nmbd After this I killed any samba-prosecces, and refreshed the inetd with:

It would seem I didn't test this thoroughly enough before I sent my email. I can reproduce the problem (same openssh version) on both Solaris 8 and Solaris 6. (I had thought it was only on Solaris 8.) I haven't checked to see if it exists on other versions of Solaris, but the problem does not exist however on RedHat 6.2 running the same openssh version. I hope that helps. Adam Benjamin

> ?????? wrote: > > Hello Sir/Madam! > > my name is dae su kim! > i have a problem diffcult! > The problem is samba process smbd and nmbd no responsing! > This log is my problem! > help me! please help me! > > problem : SAMBA_2.0.7 > > 7 03:13:48 cad1 inetd[179]: netbios-ns/udp server > failing > 7 03:27:03 cad1

Hello, My apologies if this is a known "feature" and I'm simply reporting something already known. The situation is this: - the sshd in openssh-2.3.0p1 (and also previously in openssh-2.1.1p4) fail when invoked via inetd on Solaris 8 - the sshd is invoked with: 1) an entry in /etc/services: sshback 10000/tcp sshdback # SSH Back Door 2) an entry

Hello, we would like to use rsync (2.6.2 manualy patched and recompiled) in daemon mode spawned by inetd (Solaris 5.8 Environment). /etc/services: rsync 1234/tcp #RSYNC daemon /etc/inet/inetd.conf: rsync stream tcp nowait publish /usr/bin/rsync rsyncd --daemon --port 1234 . Alas, this does not seem to work, there is the following error message in the log file:

Hi samba friends, I'm upgrading our Samba 2.2.8a server to 3.6.15 on a Solaris 9 box, we need to do this as all our latest Mac OS X 10.8 clients cannot map to the 2.2.8a network share, and need the newer Samba (well known issue for mountain lion). I've compiled 3.6.15 and this seemed to go ok, no obvious errors were shown during .configure make and make install, and smbd -V gives

Hello. I know that it is recommended to run smbd as a standalone daemon and to avoid inetd. Can you please tell me why inetd is discouraged and what problems it imposes? Also, I have one user who is having problems accessing her personal files on a MacOSX 10.3.2 via smb. Any ideas what may be causing it? Judy Lin NACS-DCS