Problems starting telnetd as a standalone service (busybox 1.16.1)

Denys Vlasenko vda.linux at googlemail.com
Fri Aug 6 12:25:36 UTC 2010


On Fri, Aug 6, 2010 at 9:46 AM, Hauser, Wolfgang (external)
<Wolfgang.Hauser.external at eads.com> wrote:
> Hello,
>
> it doesn't depend on the options, the daemon never run standalone.

It most certainly does:

# busybox telnetd --help
BusyBox v1.17.0 (2010-07-06 15:21:06 CEST) multi-call binary.

Usage: telnetd [OPTIONS]

Handle incoming telnet connections

Options:
	-l LOGIN	Exec LOGIN on connect
	-f ISSUE_FILE	Display ISSUE_FILE instead of /etc/issue
	-K		Close connection as soon as login exits
			(normally wait until all programs close slave pty)
	-p PORT		Port to listen on
	-b ADDR[:PORT]	Address to bind to
	-F		Run in foreground
	-i		Inetd mode
	-w SEC		Inetd 'wait' mode, linger time SEC
	-S		Log to syslog (implied by -i or without -F and -w)

I run it like this for testing

# busybox telnetd -F
<here it stops, waiting for connects>

In another xterm:
# telnet 127.0.0.1
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.

login: _

If for you "busybox telnetd -F" does not stop and wait, then strace it:

# strace -oLOG -s99 busybox telnetd -F

and post LOG file.

> I used start-stop-daemon of busybox, starting from shell, starting with nohup as subprocess, I got always the same problem.

Please read http://catb.org/esr/faqs/smart-questions.html

Your description does not have enough information.
Can you show me *the exact command line(s)* you use,
and *their exact output*?

-- 
vda


More information about the busybox mailing list