[mythtv-commits] Ticket #11133: Allow mythbackend network initialization to soft-fail
MythTV
noreply at mythtv.org
Mon Oct 1 22:43:45 UTC 2012
#11133: Allow mythbackend network initialization to soft-fail
------------------------------+---------------------------
Reporter: jcrews@… | Owner:
Type: Patch - Bug Fix | Status: closed
Priority: minor | Milestone: unknown
Component: MythTV - General | Version: 0.25.2
Severity: low | Resolution: Won't Fix
Keywords: | Ticket locked: 0
------------------------------+---------------------------
Comment (by jcrews@…):
Network configuration is an administrative task. The change is trivial,
but important. The main function, dvr, is maintained in all but the worst
cases of network failure. As long as one interface successfully assigns
the requested address, that should be enough for mythtv. It should (and
does) warn the operator by log message if an interface fails to assign the
requested address when listen() is called, but I see now reason for it to
quit running when it can still successfully record and run a local
frontend. The operator should decide if the failures noted are actually
important, not the software.
Regardless, mythbackend should exit when mainserver fails. Currently it
doesn't - it just runs housekeeping forever.
If for some reason the above logic is still not good enough, I propose the
following alternative:
Read the IP addresses from the database. Get the interface, and call
listen() for that interface *only* and lo, requiring all. The framework
already is in place.
---
The specific use case I'm addressing here is that if a system has a buggy
network interface that randomly fails to assign a requested address but
otherwise works (in my case a link-local IPv6 :6543,6544 occasionally
fails on one interface that's unimportant to mythtv itself).
--
Ticket URL: <http://code.mythtv.org/trac/ticket/11133#comment:2>
MythTV <http://code.mythtv.org/trac>
MythTV Media Center
More information about the mythtv-commits
mailing list