Would "ListenStream=nntp" have the same effect?
"man systemd.socket" doesn't mention an option like that. And this
directive is already overloaded with different possibilities.
The more points in common there are between inetd xinetd and systemd
configs, the less confusing it will be for tho
On Tue, 23 Oct 2012 11:51:24 +0200 Damjan wrote:
>>> Xinetd doesn't need to be told. Isn't there a table of standard ports
>>> for specified services?
>>
>> Yes, there's a table of standard ports -- it's /etc/services. It merely
>> lets you refer to ports by name rather than by number. Something
On Mon, 22 Oct 2012 19:40:37 -0400 Dave Reisner wrote:
>On Tue, Oct 23, 2012 at 12:34:20AM +0100, Whiskers wrote:
[...]
>> >> Access control depends entirely on ufw (iptables), rather than
>> >> specifying a hostname or IPv6 or IPv4 number in leafnode.socket,
>> >> although that would
>> >
>> >B
Xinetd doesn't need to be told. Isn't there a table of standard ports for
specified services?
Yes, there's a table of standard ports -- it's /etc/services. It merely
lets you refer to ports by name rather than by number. Something still
needs to indicate what port to listen on, regardless of ho
On Tue, Oct 23, 2012 at 12:34:20AM +0100, Whiskers wrote:
> On Mon, 22 Oct 2012 18:40:23 -0400 Dave Reisner wrote:
>
> >On Mon, Oct 22, 2012 at 11:19:37PM +0100, Whiskers wrote:
> >> Thank you to all those who responded :))
> >>
> >> I now have Leafnode-2 up and running smoothly with systemd.
>
On Mon, 22 Oct 2012 18:40:23 -0400 Dave Reisner wrote:
>On Mon, Oct 22, 2012 at 11:19:37PM +0100, Whiskers wrote:
>> Thank you to all those who responded :))
>>
>> I now have Leafnode-2 up and running smoothly with systemd.
>>
>> I have created these files:
>>
>> $ cat /etc/systemd/system/l
On Mon, Oct 22, 2012 at 11:19:37PM +0100, Whiskers wrote:
> Thank you to all those who responded :))
>
> I now have Leafnode-2 up and running smoothly with systemd.
>
> I have created these files:
>
> $ cat /etc/systemd/system/leafnode.socket
> [Unit]
> Description=Leafnode NNTP Socket
>
Thank you to all those who responded :))
I now have Leafnode-2 up and running smoothly with systemd.
I have created these files:
$ cat /etc/systemd/system/leafnode.socket
[Unit]
Description=Leafnode NNTP Socket
[Socket]
ListenStream=119
Accept=yes
[Install]
WantedBy=socket
On Fri, 19 Oct 2012 07:23:51 +0200 Damjan Georgievski
wrote:
>> Thanks for the pointers; something for another evening
>
>This bug has attached sysemd service files for leafnode.
>https://bugs.archlinux.org/task/24530
Interesting :)) I'll play around some more and report back.
Two points occu
> Thanks for the pointers; something for another evening
This bug has attached sysemd service files for leafnode.
https://bugs.archlinux.org/task/24530
On Thu, 18 Oct 2012 15:55:30 -0400 Dave Reisner wrote:
[...]
>Use inetd-style activation via systemd. See sshd@.service and
>sshd.socket as an example. xinetd is redundant.
Thanks for the pointers; something for another evening!
--
-- ^^
-- Whiskers
-- ~~
On Thu, Oct 18, 2012 at 08:26:16PM +0100, Whiskers wrote:
> On Thu, 18 Oct 2012 00:03:57 +0200 Thomas Bächler
> wrote:
>
> >Am 17.10.2012 21:29, schrieb Whiskers:
> >> Rather than install tcp-wrappers on my Arch system, I'd like to use
> >> whatever the proper "server" is nowadays instead of /usr
On Thu, 18 Oct 2012 00:03:57 +0200 Thomas Bächler
wrote:
>Am 17.10.2012 21:29, schrieb Whiskers:
>> Rather than install tcp-wrappers on my Arch system, I'd like to use
>> whatever the proper "server" is nowadays instead of /usr/sbin/tcpd - but
>> what is it?
>
>Why would you replace tcpd with any
Am 17.10.2012 21:29, schrieb Whiskers:
> Rather than install tcp-wrappers on my Arch system, I'd like to use
> whatever the proper "server" is nowadays instead of /usr/sbin/tcpd - but
> what is it?
Why would you replace tcpd with anything? Does it serve any purpose at all?
signature.asc
Descri
14 matches
Mail list logo
