Description of problem: Let's get the ball rolling on this one... http://fedoraproject.org/wiki/Features/SysVtoSystemd Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 522380 [details] amanda socket
Created attachment 522381 [details] amanda service
Pasess simple telnet test to port # telnet localhost 10080 Trying ::1... Connected to localhost. Escape character is '^]'. And note there is still a (tight) window to have this in F16
Created attachment 522451 [details] Amanda service
Once package and shipped you package should no longer have to depend on xinetd https://fedoraproject.org/wiki/Packaging:Guidelines:Systemd https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Systemd
I am not sure if we want to run amanda by systemd instead of xinetd. Because amanda is not enabled by default I propose that we can add unit files into the package and let user to choose.
Hum not following you dont enable amanda by default in systemd unless ofcourse you explicitly do that at install time ( or user does that by hand ) and enabling things by default requires sanctions from fesco afaik. Shipping both will only cause confusion and potential conflicts which is why we dont do that with legacy sysv init script.
I tried to pack amanda with systemd and I found out it behaves strangely. When it starts it constantly writes these two messages in its log file: amandad: dgram_recv(dgram=0x7fc334a648e8, timeout=0, fromaddr=0x7fc334a748e0) amandad: (sockaddr_in *)0x7fc334a748e0 = { 0, 0, 0.0.0.0 } After few minutes this log file occupies several gigabytes of disk space. When it is started through xinetd this issue does not occur.
Known issue with 35 http://thread.gmane.org/gmane.comp.sysutils.systemd.devel/3267/focus=3269
Hum perhaps this could be a new bug. Could you test by downgrading to .34?
I have tried this in f15, so I am using systemd-26-9.
Created attachment 523154 [details] amanda udp service
Created attachment 523155 [details] amanda udp socket
Created attachment 523156 [details] amanda tcp socket
Created attachment 523157 [details] amanda tcp service
Threw in a batch of fresh unit files to try both tcp and udp based
It seems that tcp works fine. With udp amanda won't start when I try to connect, but I wasn't able to find why.
Created attachment 523349 [details] new amanda udp socket
Ok good to know that tcp works I have created a new udp socket file without multiple Listen datagram entries.
I think this will be a bit more complicated. This unit file is for amandad, which is client daemon in amanda. If we want to switch to systemd completely, we will need unit files for all daemons included in amanda (amandaidxd, amidxtaped) and this configuration should be compatible with amanda started by xinetd from older realeases of Fedora and RHEL.
amanda-3.3.2-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/amanda-3.3.2-1.fc18
Package amanda-3.3.2-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing amanda-3.3.2-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-11996/amanda-3.3.2-1.fc18 then log in and leave karma (feedback).
amanda-3.3.2-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.