supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Leah Neukirchen <leah@vuxu.org>
To: peter@easthope.ca
Cc: supervision@list.skarnet.org
Subject: Re: Status of daemon.
Date: Mon, 04 Nov 2024 18:25:59 +0100	[thread overview]
Message-ID: <87ses6zza0.fsf@vuxu.org> (raw)
In-Reply-To: <6728fd36.050a0220.1c7799.f358SMTPIN_ADDED_MISSING@mx.google.com> (peter@easthope.ca's message of "04 Nov 2024 08:58:27 -0700")

peter@easthope.ca writes:

> In Void, installed inetutils-telnet.
>
> # telnet localhost
> Trying ::1...
> Connection failed: Connection refused
> Trying 127.0.0.1...
> telnet: Unable to connect to remote host: Connection refused
> #
> # ps aux | grep telnetd
> root       754  0.0  0.0   2388  1280 ?        Ss   07:18   0:02 runsv telnetd
> root       773  0.0  0.0   2508  1280 ?        S    07:18   0:00 vlogger -t telnetd -p daemon
> root     32002  0.0  0.0   6600  2432 pts/3    S+   08:32   0:00 grep telnetd
>
> telnetd is running and declined the connection request?

This does not suggest telnetd is running, as no process of these is
telnetd.

Use "sv status telnetd" to check, it probably says "down: ...".

> Can I learn more from a log?  If so, how is the log accessed?
> cat ... ?

If you still use socklog-unix, look at /var/log/socklog/daemon/current

Else try to start the telnetd run script manually and look for errors:
/var/service/telnetd/run

Else post the script, it seems to be manually created.

As telnetd classically needs to be started from inetd, you need to use
some tcpserver to launch it (djb tcpserver or s6-tcpserver).

hth,
-- 
Leah Neukirchen  <leah@vuxu.org>  https://leahneukirchen.org/

       reply	other threads:[~2024-11-04 17:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6728fd36.050a0220.1c7799.f358SMTPIN_ADDED_MISSING@mx.google.com>
2024-11-04 17:25 ` Leah Neukirchen [this message]
2024-11-04 15:58 peter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ses6zza0.fsf@vuxu.org \
    --to=leah@vuxu.org \
    --cc=peter@easthope.ca \
    --cc=supervision@list.skarnet.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).