xinetd 1:2.3.15-4 source package in Ubuntu
Changelog
xinetd (1:2.3.15-4) unstable; urgency=low
* Add xinetd upstart job from Ubuntu
* Bump Standards-Version to 3.9.6
* Moved update-inetd to recommends. inetd compat mode is
not compulsory.
-- Salvo 'LtWorf' Tomaselli <email address hidden> Thu, 17 Sep 2015 09:08:48 +0200
See full publishing history Publishing
| Series | Published | Component | Section |
|---|
Downloads
| File | Size | SHA-256 Checksum |
|---|---|---|
| xinetd_2.3.15-4.dsc | 1.8 KiB | a83f6cf227933e05adef0618f808a25d2d274f8b8d052c90eb2444dd3966218b |
| xinetd_2.3.15.orig.tar.gz | 302.5 KiB | bf4e060411c75605e4dcbdf2ac57c6bd9e1904470a2f91e01ba31b50a80a5be3 |
| xinetd_2.3.15-4.debian.tar.xz | 22.9 KiB | c5ba69023a5e788ec003efb27eab6ccd8e352ee55807c102ac5267ed00177737 |
Available diffs
No changes file available.
Binary packages built by this source
- xinetd: replacement for inetd with many enhancements
xinetd has access control mechanisms, extensive logging capabilities,
the ability to make services available based on time, and can place
limits on the number of servers that can be started, among other things.
.
It has the ability to redirect TCP streams to a remote host and port.
This is useful for those of that use IP masquerading, or NAT, and want
to be able to reach your internal hosts.
.
It also has the ability to bind specific services to specific interfaces.
This is useful when you want to make services available for your internal
network, but not the rest of the world. Or to have a different service
running on the same port, but different interfaces.
- xinetd-dbgsym: debug symbols for package xinetd
xinetd has access control mechanisms, extensive logging capabilities,
the ability to make services available based on time, and can place
limits on the number of servers that can be started, among other things.
.
It has the ability to redirect TCP streams to a remote host and port.
This is useful for those of that use IP masquerading, or NAT, and want
to be able to reach your internal hosts.
.
It also has the ability to bind specific services to specific interfaces.
This is useful when you want to make services available for your internal
network, but not the rest of the world. Or to have a different service
running on the same port, but different interfaces.
