similar to: tftp-hpa 5.2

I sure did check the firewall and selinux as well. As an extreme testing major, they are both turned off. $ systemctl status firewalld firewalld.service - firewalld - dynamic firewall daemon ? ?Loaded: loaded (/usr/lib/systemd/system/firewalld.service; disabled) ? ?Active: inactive (dead) sestatus? SELinux status: ? ? ? ? ? ? ? ? disabled Actually, now tftp transfers are denied $ tftp 127.0.0.1

Hi, today I updated the glibc packages on some CentOS machines. After the Update I checked which services/processes I have to restart "yum -C ps" or "needs-restarting" At the most machines I get no information about necessary restarts, but at two machines a long listing : 1 : /sbin/init 386 : /sbin/udevd-d 659 : /sbin/udevd-d 999 : /usr/sbin/vmtoolsd 1103 : auditd 1128 :

I'm upgrading my primary server from RH 7.2 to CentOS-4.3.ServerCD. I REALLY like the ServerCD. Who needs all the fluff that comes with a standard distro? If I want a system-config-gooey I can run Xnest [1] and ssh -X from my laptop. Anyway I have two questions: 1) How can I collectively stop all the NFS, portmap, whatever? I'm hoping it can be manipulated as a group because occationally

> Correct. Like most UDP-based inetd services, tftpd is intended to be run in 'wait' mode. When the first request arrives, inetd starts the service but does not read the incoming packet (it can't, because it has no way to pass it along to the server). After that, inetd ignores that socket until the server exits. This isn't critical for tftp, but it does help to keep down the

Good day, Just a quick question- could someone please confirm that this is the correct xinetd configuration (or not) for hpa-tftp? We've noticed that, when under moderate load hpa-tftpd resides in memory, even after there are no connections or even if xinetd is shut down. Under light load the server goes away after each connection, as desired. Thanks in advance! service tftp {

I just submitted a PR for this (haven't even gotten the confirmation email), but since not everyone tracks the GNATS CVS distribution, I figured that I'd send it here as well. -----Forwarded Message----- > From: Steve Grubb <linux_4ever@yahoo.com> > To: bugtraq@securityfocus.com > Subject: Xinetd 2.3.10 Memory Leaks > Date: 18 Apr 2003 16:18:36 +0000 > > >

Hi, I have a tftp client which loads quite happily from a tftpd built from netkit-tftp-0.16 but which fails to load from from a tftpd built from tftp-hpa 0.29. In both cases, tftpd was built from pristine sources and run from xinetd under Redhat 7.3. [netkit-tftp-0.16 is the ancestor of tftp-hpa, predating HPA's maintenance of same] [the tftp client also.. .. fails with the prebuilt tftpd

Hopefully I'm not out to lunch here. I ported tftp-hpa to our proprietary OS, VOS (at stratus.com). We've always runs the old legacy tftpd from inetd, so I wanted to continue doing so with tftp-hpa. It seems to work okay, but I noticed that the code in tftpd.c has a 'while (1)' loop that has this at the end: /* * Now that we have read the request packet from

Hello, I am trying to flash new firmware into a router using TFTP-HPA. I am running Ubuntu 14.04 on a flash drive and still learning how to use Linux. I have also installed XINETD.D In one of the README files that comes with TFTP-HPA it said not to call it using tptp. Here are the instructions I'm trying to follow: cd /tmp ; tftp -gl aa 192.168.0.9; sh aa I do not know what

List, The past few days the asterisk service on my server has crashed several times. I have had it running for months and have made no changes to it. When it crashes, I am unable to make calls or gain access to the CLI. The service has been stopped. If I try to start it again (service asterisk start), it will start and run for a few seconds then crash again. After a reboot, it will run

Still having trouble: >> cd /tmp >> ping -c 3 192.168.0.9 # check if TFTP server respons on ping >> tftp 192.168.0.9 # connect to TFTP server, you should get a new prompt OK to here using 192.168.1.9 for NIC eth(0) and tftpd server 192.168.1.9 New prompt is tftp> >> get aa This times out and returns to tftp> Unable to return to shell using exit

I had this problem fixed by setting the ownership of the root tftp directory, "must be set to nobody as this is the default user ID setup by tftpd" as specified in this tutorial http://blackfin.uclinux.org/doku.php?id=setting_up_a_tftp_server However, I do not know if the ownership set to nobody is essential with Fedora because SELinux requires it or if it is a general good practice for

Hi everyone, In the last few days I've spended hours and hours on the web surching for a solution to my problems. Eventhough it looked like there where several other people having the same problem I couldn't find a way to solve it. Therefore I'm hoping that one of you could help me with the following problem. I've installed Samba 3.0.14a on RedHat 9.0. Samba is working perfectly.

I am using centos 5.1 x86_64 I am wanting to restart xinetd when I do "service xinetd restart" it says xinetd unrecognized service when I do "/etc/init.d/xinetd restart" I get no such file or directory. How does one restart xinetd? THanks, Jerry

Hi: I have something like this: class xinetd { ... some Puppet code ... class xinetd::telnet { ... some Puppet code ... } } node ''host1'' { include xinetd::telnet } However, when running Puppet says it can''t find class xinetd::telnet. I can include xinetd so I know my site.pp correctly includes all .pp files. I am running Puppet 2.6.0. Thanks

Staging for a rollout of EL 6, and ran into a very strange permissions issue with xinetd that defies all (my) logic. It's a script called "spfiled" that we use for messaging between our server cluster servers. I'm trying to get it to run with "least permissions necessary". Because it reads/writes files in conjunction with a web-based service, it runs as user

hi, i upgraded to samba 2.2.7 and since this nmbd (configured to start from xinetd) doesn't start! i sent SIGHUP to xinetd and can see that configuration is ok (netbios-ns is readjusted) but nmbd doesn't start!! when i start nmbd by hand with "-D" i see many messages from xinetd in /var/log/secure: Dec 3 12:05:39 atpcw6yc xinetd[1724]: START: netbios-ns pid=1973

I am interested in opinions regarding the use of xinetd versus the use of tcp wrappers. The two programs have similar functionality, but I find xinetd suits my needs better. The biggest problem is the age of xinetd, and AFAIK it is no longer being kept up. Are there any known security issues with xinetd? Another issue is that xinetd makes use of a non-standard inetd.conf layout, but

Hello, I've succefuly installed samba 2.2.2 on my Linux box. I can share between Linux and MS boxes, but I want to start samba from xinetd. In /etc/xinetd.d/ I have this: #/etc/xinetd.d/netbios-ns service netbios-ns { disable = no socket_type = dgram protocol = udp port = 137 user = root wait

IT WORKS!!!!!!!!!!! But before I say what I did... yall have to promise not to laugh! (MAH!! I HEAR YOU!!) ... anyone ever heard of.... /etc/rc.d/init.d/xinetd restart I can tell you from experience that 'killall -HUP xinetd' is NOT the same. I can also say that nobody will find that command line entry in "Using Samba". To show my appreciation to the groups involved,