06-08-2009
use vsftpd. It is the 'default' one. It is not run out of xinetd. /etc/init.d/vsftpd start/ stop
10 More Discussions You Might Find Interesting
1. Cybersecurity
i want to edit inetd.conf for security on my redhat 7.1 box, but i dont have it in my /etc directory, rather, i have xinetd.conf. Can i use xinetd.conf for the same purpose, is it as useful as inetd.conf? (2 Replies)
Discussion started by: lealyz
2 Replies
2. Linux
hey,
haha it's me agian, i think that my xinetd is messed up, i am unable to stop it. I can start it though...lol. I just wonderd how can i uninstall it so i can reinstall it...maybe this time it'll work. I'm running RH 7.1 i think.
thanks:) (5 Replies)
Discussion started by: byblyk
5 Replies
3. Linux
hi...
i am trying to find out the services which should be started before the service xinetd can be started.
I have read thru the /etc/rc.d/init.d script and i think xinetd depends on service network as it checks whether the variable NETWORKING is set or not
|| exit 0
Does it... (0 Replies)
Discussion started by: tuxfood
0 Replies
4. UNIX for Advanced & Expert Users
I do make sure that in my system (redhat 9.0 with eveything installed)
file cvspserver with correct content
in directory /etc/xinetd.d/
line
cvspserver 2401/tcp
cvspserver 2401/udp
in file /etc/service
I aslo restart service xinetd
but when I issue command ... (1 Reply)
Discussion started by: victorvvk
1 Replies
5. Shell Programming and Scripting
Hello there,
I hope I took the right forum...
I never worked with Perl, but now I have to get a simple fileserver running. The goal is to deliver an XML file (it's part of a new security model in the Flashplayer, see Adobe - Developer Center : Setting up a socket policy file server for more... (9 Replies)
Discussion started by: blemmo
9 Replies
6. Linux
Hi,
Once again I came to get rescued in a situation where one of my workstations has this ierd thing that "xinetd" won't start at reboot or shutdown. I have done the follwoing but no change in results.
chkconfig --list xinetd
xinetd 0:off 1:off 2:on 3:on 4:on 5:on ... (2 Replies)
Discussion started by: harjitsingh
2 Replies
7. Emergency UNIX and Linux Support
i solved myself.
thx! (2 Replies)
Discussion started by: pabloli150
2 Replies
8. Red Hat
Hello everyone.. I need some help in understanding the usage of tcp46 socket and xinetd.d flags..
What I'm trying to do?
I'm looking to use tenet via tcp46 socket for both ipv4 and ipv6 traffic. For this, if i set flags = IPV6 xinetd.d, telnet service, i can not telnet via V4. If I unset the... (0 Replies)
Discussion started by: Sudharshan
0 Replies
9. Red Hat
Dear all,
I am reciving the following error in the /var/log/messages of my system
Jul 18 11:14:27 airtest xinetd: START: echo-dgram pid=0 from=::ffff:XX.XX.XX.X
Jul 18 11:14:27 airtest xinetd: START: echo-dgram pid=0 from=::ffff:XX.XX.XX.X
Jul 18 11:19:17 airtest xinetd: START: echo-dgram... (1 Reply)
Discussion started by: pistachio
1 Replies
10. Solaris
I got the xinetd src from synack archive but when I try to compile I get errors all over the place, so am just wondering if anyone has a pre patched working version of xinetd for solaris 7 or higher there can share ???
thanks (4 Replies)
Discussion started by: Wpgn
4 Replies
LEARN ABOUT CENTOS
dh_systemd_start
DH_SYSTEMD_START(1) Debhelper DH_SYSTEMD_START(1)
NAME
dh_systemd_start - start/stop/restart systemd unit files
SYNOPSIS
dh_systemd_start [debhelperoptions] [--restart-after-upgrade] [--no-stop-on-upgrade] [unitfile...]
DESCRIPTION
dh_systemd_start is a debhelper program that is responsible for starting/stopping or restarting systemd unit files in case no corresponding
sysv init script is available.
As with dh_installinit, the unit file is stopped before upgrades and started afterwards (unless --restart-after-upgrade is specified, in
which case it will only be restarted after the upgrade). This logic is not used when there is a corresponding SysV init script because
invoke-rc.d performs the stop/start/restart in that case.
OPTIONS
--restart-after-upgrade
Do not stop the unit file until after the package upgrade has been completed. This is the default behaviour in compat 10.
In earlier compat levels the default was to stop the unit file in the prerm, and start it again in the postinst.
This can be useful for daemons that should not have a possibly long downtime during upgrade. But you should make sure that the daemon
will not get confused by the package being upgraded while it's running before using this option.
--no-restart-after-upgrade
Undo a previous --restart-after-upgrade (or the default of compat 10). If no other options are given, this will cause the service to
be stopped in the prerm script and started again in the postinst script.
-r, --no-stop-on-upgrade, --no-restart-on-upgrade
Do not stop service on upgrade.
--no-start
Do not start the unit file after upgrades and after initial installation (the latter is only relevant for services without a
corresponding init script).
NOTES
Note that this command is not idempotent. dh_prep(1) should be called between invocations of this command (with the same arguments).
Otherwise, it may cause multiple instances of the same text to be added to maintainer scripts.
Note that dh_systemd_start should be run after dh_installinit so that it can detect corresponding SysV init scripts. The default sequence
in dh does the right thing, this note is only relevant when you are calling dh_systemd_start manually.
SEE ALSO
debhelper(7)
AUTHORS
pkg-systemd-maintainers@lists.alioth.debian.org
11.1.6ubuntu2 2018-05-10 DH_SYSTEMD_START(1)