inetd.conf manuell zu xinetd.conf

M

Masta_O

Registered User
Hallo!

Ich hab eben versucht meinen inetd auf xinetd umzustellen.

Hab mir dazu de:howtos:woody:xinetd [Debianhowto.de] durchgelesen und dachte: easy.

Also apt-get install xinetd

Code: 
(Reading database ... 64053 files and directories currently installed.)
Unpacking xinetd (from .../xinetd_1%3a2.3.14-1_i386.deb) ...
Setting up xinetd (2.3.14-1) ...
Stopping internet superserver: xinetd.
Adding `diversion of /etc/init.d/inetd to /etc/init.d/inetd.real by xinetd'
Starting internet superserver: xinetd.
Von der Frage ob ich meine inetd.conf in xinetd.conf convertieren möchte, keine Spur.
Kann ich das Convertierungsprogramm auch manuell anstoßen? Wenn ja, wie?
 
Wenn alles korrekt installiert wurde, sollte folgendes funktionieren:
Code: 
/usr/sbin/xconv.pl < /etc/inetd.conf > /tmp/xinetd.conf
--marneus
 
Danke für den Hinweis!

Die daraus generierte xinetd.conf habe ich an die Stelle der alten xinetd.conf /etc/xinetd.conf gelegt.

Code: 
# This file generated by xconv.pl, included with the xinetd
# package.  xconv.pl was written by Rob Braun (bbraun@synack.net)
#
# The file is merely a translation of your inetd.conf file into
# the equivalent in xinetd.conf syntax.  xinetd has many 
# features that may not be taken advantage of with this translation.
# Please refer to the xinetd.conf man page for more information 
# on how to properly configure xinetd.


# The defaults section sets some information for all services
defaults
{
	#The maximum number of requests a particular service may handle
	# at once.
	instances   = 25

	# The type of logging.  This logs to a file that is specified.
	# Another option is: SYSLOG syslog_facility [syslog_level]
	log_type    = FILE /var/log/servicelog

	# What to log when the connection succeeds.
	# PID logs the pid of the server processing the request.
	# HOST logs the remote host's ip address.
	# USERID logs the remote user (using RFC 1413)
	# EXIT logs the exit status of the server.
	# DURATION logs the duration of the session.
	log_on_success = HOST PID

	# What to log when the connection fails.  Same options as above
	log_on_failure = HOST

	# The maximum number of connections a specific IP address can
	# have to a specific service.  
	per_source  = 5
}

service ident
{
	socket_type = stream
	protocol    = tcp
	wait        = yes
	user        = identd
	server      = /usr/sbin/identd
	server_args = identd 
	disable     = yes
}

service poppassd
{
	socket_type = stream
	protocol    = tcp
	wait        = no
	user        = root
	server      = /opt/psa/admin/bin/poppassd
}

service smtp
{
	socket_type = stream
	protocol    = tcp
	wait        = no
	user        = root
	server      = /var/qmail/bin/tcp-env
	server_args = tcp-env /usr/bin/env SMTPAUTH=1 POPLOCK_TIME=20 SHORTNAMES=1 END=1 /var/qmail/bin/relaylock /var/qmail/bin/qmail-smtpd /var/qmail/bin/smtp_auth /var/qmail/bin/true /var/qmail/bin/cmd5checkpw /var/qmail/bin/true 
}

service smtps
{
	socket_type = stream
	protocol    = tcp
	wait        = no
	user        = root
	server      = /var/qmail/bin/tcp-env
	server_args = tcp-env /usr/bin/env SMTPAUTH=1 POPLOCK_TIME=20 SHORTNAMES=1 END=1 /var/qmail/bin/relaylock /var/qmail/bin/qmail-smtpd /var/qmail/bin/smtp_auth /var/qmail/bin/true /var/qmail/bin/cmd5checkpw /var/qmail/bin/true 
}

service ftp
{
	socket_type = stream
	protocol    = tcp
	wait        = no
	user        = root
	server      = in.proftpd
}

service 111
{
	socket_type = stream
	protocol    = tcp
	port        = 111
	type        = UNLISTED
	wait        = no
	user        = root
	server      = /opt/b1gmailserver/bin/b1gmailserver
	server_args = --pop3 
}

service 144
{
	socket_type = stream
	protocol    = tcp
	port        = 144
	type        = UNLISTED
	wait        = no
	user        = root
	server      = /opt/b1gmailserver/bin/b1gmailserver
	server_args = --imap 
}

service 112
{
	socket_type = stream
	protocol    = tcp
	port        = 112
	type        = UNLISTED
	wait        = no
	user        = root
	server      = /opt/b1gmailserver/bin/b1gmailserver
	server_args = --pop3 
}

service 145
{
	socket_type = stream
	protocol    = tcp
	port        = 145
	type        = UNLISTED
	wait        = no
	user        = root
	server      = /opt/b1gmailserver/bin/b1gmailserver
	server_args = --imap 
}
Leider geht weder FTP, noch SMTP.

Ich habe es mit einem xinetd restart versucht, oder gibt es noch eine extra "confreload" Befehl für den xinetd?

Müssen auch die Dateien aus /etc/init.d/ nach etc /xinit.d/ kopiert werden?
 
Masta_O said:
Müssen auch die Dateien aus /etc/init.d/ nach etc /xinit.d/ kopiert werden?
Click to expand...

Obacht, "init" hat nichts mit "inetd" zu tun. Der init-Prozess ist der Prozess, der vom Kernel direkt nach dem Booten gestartet wird; er hat die Prozess-ID "1" und von ihm gehen direkt und indirekt alle weiteren Prozesse des Systems aus.
Der inetd wird als Internet-Super-Daemon bezeichnet, der Anstelle verschiedener Programme auf Anfragen wartet und dann die Programme mit den entsprechenden Parametern aufruft. Der xinetd ist eine Variante davon.

Einen direkten Hinweis zur Lösung Deines Problems kannst Du höchstwahrscheinlich in der Logdatei des xinetd (s. Config-Datei) oder der allgemeinen syslog/messages-Datei finden.
 
Alter Thread, egal ich habs gefixt.

Howto:

Du hast inetd anstatt xinetd, dein Mailverkehr ist lahm.

aptitude install xinetd
##
remove openbsdinetd bestätigen


cat /dev/null > /etc/xinetd.conf

vim /etc/xinetd.conf

Code: 
defaults
{
        log_type        = FILE /var/log/xinetd.log
        log_on_success  = HOST EXIT DURATION
        log_on_failure  = HOST ATTEMPT
        instances       = 30
        cps             = 50 10

}

includedir /etc/xinetd.d
cd /etc/xinetd.d
vim ftp_psa
Code: 
service ftp
{
        disable         = no
        socket_type     = stream
        protocol        = tcp
        wait            = no
        user            = root
        instances       = UNLIMITED
        server          = /usr/sbin/in.proftpd
        server_args     = -c /etc/proftpd.conf
}
vim poppassd_psa
Code: 
service poppassd
{
socket_type             = stream
protocol                = tcp
port                    = 106
wait                    = no
disable                 = no
user                    = root
instances               = 1000
flags                   = KEEPALIVE
server                  = /usr/local/psa/admin/bin/poppassd
}
vim smtp_psa
Code: 
service smtp
{
        socket_type     = stream
        protocol        = tcp
        wait            = no
        disable         = no
        user            = root
        instances       = UNLIMITED
        env             =  SMTPAUTH=1
        server          = /var/qmail/bin/tcp-env
        server_args     = -Rt0 /var/qmail/bin/relaylock /var/qmail/bin/qmail-smtpd /var/qmail/bin/smtp_auth /var/qmail/bin/true /var/qmail/bin/cmd5checkpw /var/qmail/bin/true
}
vim smtps_psa
Code: 
service smtps
{
        socket_type     = stream
        protocol        = tcp
        wait            = no
        disable         = no
        user            = root
        instances       = UNLIMITED
        env             =  SMTPAUTH=1
        server          = /var/qmail/bin/tcp-env
        server_args     = -Rt0 /var/qmail/bin/relaylock /var/qmail/bin/qmail-smtpd /var/qmail/bin/smtp_auth /var/qmail/bin/true /var/qmail/bin/cmd5checkpw /var/qmail/bin/true
}
vim submission.psa
Code: 
service submission
{
        socket_type     = stream
        protocol        = tcp
        wait            = no
        disable         = no
        user            = qmaild
        instances       = UNLIMITED
        env             = SUBMISSION=1 SMTPAUTH=1
        server          = /var/qmail/bin/tcp-env
        server_args     = -Rt0 /var/qmail/bin/qmail-smtpd /var/qmail/bin/smtp_auth /var/qmail/bin/true /var/qmail/bin/cmd5checkpw /var/qmail/bin/true
}
/etc/init.d/xinetd restart


Damit dürften jetzt alle psa superuserdienste abgehandelt worden sein.
 
You must log in or register to reply here.
Back
Top