FS#32233 - [mythtv] - mythbackend requires alternative config file for systemd/netcfg static ip
Attached to Project:
Community Packages
Opened by John (graysky) - Friday, 26 October 2012, 19:20 GMT
Last edited by Jonathan Conder (PirateJonno) - Monday, 26 November 2012, 01:43 GMT
Opened by John (graysky) - Friday, 26 October 2012, 19:20 GMT
Last edited by Jonathan Conder (PirateJonno) - Monday, 26 November 2012, 01:43 GMT
|
Details
Description: This is related to
https://bugs.archlinux.org/task/31846
wherein the package provided
/usr/lib/systemd/system/mythbackend.service causes
mythbackend to start before my static network configuration
from netcfg is ready which causes frontends connectivity
problems.
The fix is the attached patch. Additional info: * package version(s) 1:0.26.0-2 |
This task depends upon
Closed by Jonathan Conder (PirateJonno)
Monday, 26 November 2012, 01:43 GMT
Reason for closing: Duplicate
Additional comments about closing: This patch is not a good solution. We can continue the discussion at FS#31846
Monday, 26 November 2012, 01:43 GMT
Reason for closing: Duplicate
Additional comments about closing: This patch is not a good solution. We can continue the discussion at
Comment by
Jonathan Conder (PirateJonno) -
Wednesday, 31 October 2012, 23:58 GMT
How does this affect users who don't use netcfg? Also, the patch
looks backwards if I'm not mistaken (no big deal - just checking).
I would suggest adding something to make network.target depend on
netcfg (see /usr/lib/systemd/system/NetworkManager.service for an
example of how this might be done - I'm no expert), rather than
assuming the user is using netcfg (for example I prefer
networkmanager).