similar to: Solaris removing ktkt_warnd from inetd.conf

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

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

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

I was reading thru the manual following the directions for installing Samba and for Mac OS X you are supposed to set the inetd.conf file and the services file. I did so but when ever I reboot the computer it never starts up the samba or swat. Anyone have any other ideas on what to do? Thanks Steffan --------------------------------------------------------------- T E L 6 0 2 . 5 7 9 . 4 2 3 0

I have a RedHat 9.0 machine and just updated to samba-3.0.5pre1. I had been running Samba to network two Windoze computers and using a network printer. Two weeks ago my house was apparently hit by lightning which created havoc with my computer/server. I got it going again but have noticed several lingering problems. For one thing, I can't print from it. I was going to check things

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

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

When using rsync 2.5.2 as daemon on a Solaris 2.5.1 box, I cannot copy data to rsync volumes with option 'use chroot'; I get the following messages on the client: pipe failed in do_recv rsync error: error in socket IO (code 10) at main.c(375) rsync: connection unexpectedly closed (69 bytes read so far) What seems to occur on the server is that socketpair(3) (not pipe(2)) is called,

> ?????? 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

> 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

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:

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

Is there any option for dovecot to exit when is unneded? I mostly use dovecot via shell process (ie. something like /usr/sbin/dovecot --exec-mail imap) But sometimes I want to use it remotely via tcp and I run dovecot via inetd. --8<---------------cut here---------------start------------->8--- localhost:imap stream tcp nowait root /usr/sbin/tcpd

Hi, I'm running a Active Directory domain on Samba 4.0.1 and I'm trying to join a Solaris 11 machine this domain: # smbadm join -u Administrator DOMAIN After joining DOMAIN the smb service will be restarted automatically. Would you like to continue? [no]: yes Enter domain password: Locating DC in DOMAIN ... this may take a minute ... Joining DOMAIN ... this may take a minute ... failed

I was searching for help on Mandrake's site and got nowhere other than seeing this really weird help-page loop where it showed the pages you could go to, BUT would not show any information from the page.... Just use the search from www.mandrake.com to see this strangeness.... No helpful... Anyway.. trying to run drakconf and startup services to start either inetd or xinetd seems to be

I'm currently running version 2.0.7 of samba(CIFS9000). I have HPUX 11.x installed on the samba server. When I try to run this from inetd it doesn't work. I can run a startup script that runs the smbd as a daemon and it works fine. But if I try to run it from inetd it won't start. The previous version of Samba 1.9.18p10 that I had on this server worked fine. Is this a bug in

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) ---

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