Bug 91400
| Summary: | xinetd doesn't restart killed tftp server | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Götz Waschk <waschk> |
| Component: | xinetd | Assignee: | Jay Fenlason <fenlason> |
| Status: | CLOSED NOTABUG | QA Contact: | Brock Organ <borgan> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.3 | CC: | jfeeney |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2003-06-05 14:47:10 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
OK, I've found the problem: there was a wait=no entry in /etc/xinetd.d/tftp. This didn't cause problems until the update to 2.3.11. I don't know where this came from, as the default correct setting is wait=yes. |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.4b) Gecko/20030508 Description of problem: Since the security update to 2.3.11-1.7x, my tftp server process doesn't restart after it was killed. I have to restart xinetd instead. Version-Release number of selected component (if applicable): xinetd-2.3.11-1.7x How reproducible: Always Steps to Reproduce: 1. tftp localhost 2. get somefile 3. quit 4. killall in.tftpd 5. tftp localhost 6. get somefile Actual Results: I get a connection timeout message, there's no in.tftpd running. Expected Results: It should restart in.tftpd and the result of step 2 and 6 should be the same. Additional info: This was working fine with xinetd-2.3.7-4.7x, the previous version I had installed.