03-31-2004
haha, i just fixed my telnet...lol you know what was wrong! I didn't have the telnet-server rpm installed. I thought that it was all included in the telnet RPM ooops my bad...lol. thank you so much for your help everybody! I learned lots!
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
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
3. 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
4. Solaris
Hello,
I'm working on a Solaris 9/Sparc machine and it has the Solaris 10 version of Perl (5.8.8) installed on it, which always requires all kinds of library files that Solaris 9 doesn't come with. I think the best way to do is to uninstall this wrong version and install the correct Solaris 9... (1 Reply)
Discussion started by: alanlh
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. Red Hat
Hello all,
I´m trying to configure the ftp service (port 21) in a Red Hat Enterprise 4 from xinetd.
Anybody have done this?
Thank you in advance. (3 Replies)
Discussion started by: mig28mx
3 Replies
8. Emergency UNIX and Linux Support
i solved myself.
thx! (2 Replies)
Discussion started by: pabloli150
2 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
nstrtel(5) File Formats Manual nstrtel(5)
NAME
nstrtel - specifies the number of telnet device files the kernel can support for incoming telnet sessions
VALUES
Failsafe
Default
Allowed values
(Subject to available physical memory.)
It is best to use the default value, and there should not be any need to lower it. However, if the simultaneous telnet connection load is
very high, then the value of could be increased.
Recommended values
(Default value.)
DESCRIPTION
The telnet daemon uses two STREAMS-based pseudo-terminal drivers and The kernel parameter, can be used to tune the number of pseudo-termi-
nals. specifies the number of kernel data structures that are created at system boot time that are required to support the device files
used by incoming telnet sessions on a server. If the command or SAM is used to create more telnet device files, the value of must be
increased accordingly or the device files cannot be used because there are no kernel data structures available for communicating with the
system.
Who Is Expected to Change This Tunable?
Anyone.
Restrictions on Changing
Changes to this tunable take effect at the next reboot.
When Should the Value of This Tunable Be Raised?
When there is an increase in the load of telnet connections and there are no device files available to open telnet connections, then this
kernel parameter should be increased.
When the error is encountered, then the device files have been exhausted and should be raised. Once the value of is raised, should be run
to create new device files. (If SAM is used to raise the value of is run automatically.)
What Are the Side Effects of Raising the Value of This Tunable?
More resources would be consumed. Extra kernel data structures, and extra device files may clog the system.
When Should the Value of This Tunable Be Lowered?
It is not advisable to lower the tunable value from the default value. Consult HP Support before lowering this tunable from the default
value.
What Are the Side Effects of Lowering the Value of This Tunable?
Though not recommended, there would not be any side effects.
What Other Tunables Should Be Changed at the Same Time?
None.
WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of
HP-UX.
Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation,
some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun-
able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was
factory installed on your system, see at
AUTHOR
was developed by HP.
SEE ALSO
insf(1M), telnetd(1M), telm(7), tels(7).
Tunable Kernel Parameters nstrtel(5)