Am 2016-12-14 um 07:47 schrieb Jon LaBadie: > On my Fedora systems (amanda clients) there seem to be > 6 SystemD unit files associated with amanda (output > reordered and grouped). My CentOS amanda server > has only the first 4. > > $ systemctl list-unit-files | grep aman > amanda-udp.service static > amanda-udp.socket enabled > > [email protected] static > amanda.socket enabled > > [email protected] static > kamanda.socket disabled > > Until I enabled and started the socket units, my server > could not connect with the client (client reset error). > > What is "amanda-udp"?
If you use bsdudp-authentication the socket has to be configured differently. > Why are two services listed as "@.service"? > How are these used? > > What is kamanda? My googling lets me assume that this is for kerberos authentication. > Why does a socket need to be enabled? > Need both amanda and amanda-udp? > Why not just xinetd and firewall settings? > > Jon, who is not liking having to do so many not understood > things. I hate doing "try this and see if it works". Jon, instead of hate there is documentation :-) https://www.freedesktop.org/software/systemd/man/systemd.service.html https://www.freedesktop.org/software/systemd/man/systemd.socket.html answer questions for enabling and the "@" at least. If you wouldn't have to enable and start it, how could you on the other hand tell the system to *not* provide these services? They can't be enabled and running per default, right? Just think of it as setting "disable = no" in /etc/xinetd.d/amanda and starting xinetd ... same steps. I just checked a amanda-client, there I only have enabled # systemctl status amanda.socket ● amanda.socket - Amanda Socket Loaded: loaded (/usr/lib64/systemd/system/amanda.socket; enabled; vendor preset: disabled) Active: active (listening) since Thu 2016-06-23 08:14:09 CEST; 5 months 21 days ago Listen: [::]:10080 (Stream) Accepted: 1881; Connected: 0 and it contains: # cat /usr/lib64/systemd/system/amanda.socket [Unit] Description=Amanda Socket [Socket] ListenStream=10080 Accept=true [Install] WantedBy=sockets.target -- done, nothing else needed on that client afaik To me that is way more clean and efficient that having to run and configure an extra daemon (xinetd). But: you are still free to enable and start xinetd.service and configure your amandad in the xinetd.conf, if you prefer, as it was done pre-systemd (you have to disable and stop the socket then, as it would conflict with xinetd otherwise, listening on the same port). Then xinetd listens on the configured port(s) instead of systemd itself. The usage of systemd-sockets let's you get rid of xinetd, and you get the advantages of being able to control and log the amanda.socket through systemd (systemctl, journalctl etc) good luck, systemd isn't that bad ... give it some learning curve. Stefan
