2012-01-22 - [GRASE-Hotspot] #45: Network settings aren’t always applied
Header Data
From: GRASE Trac <tr***c@grasehotspot.org>
Message Hash: bb05c9fdc090e1b5f07d5f426099c8ea206b239033c2d61dc6011d5912c57770
Message ID: <039.4f80f835909fbd90b9f04d6d3a33c243@grasehotspot.org>
Reply To: N/A
UTC Datetime: 2012-01-22 16:46:47 UTC
Raw Date: Sun, 22 Jan 2012 23:46:47 -0000
Raw message
#45: Network settings aren't always applied
------------------------------------------------------+-----------------
Reporter: tim | Owner: tim
Type: defect | Status: new
Priority: critical | Milestone: 3.7
Component: Other Backend | Version: 3.6
Keywords: network settings, chilli, dnsmasq, mysql |
------------------------------------------------------+-----------------
Due to MySQL not always running before chilli/dnsmasq, attempting to get
the Network Settings (which are stored in MySQL) via the
networksettings.dnsmasq.php script will fail and cause odd behaviour.
Need to add error checking to the script return, and make chilli only use
the /etc/dnsmasq.d/01-grasehotspot file
--
Ticket URL: <http://trac.grasehotspot.org/ticket/45>
GRASE Hotspot <http://grasehotspot.org/>
GRASE Hotspot bug tracker
Thread
-
Return to January 2012
-
Return to “GRASE Trac <tr***c@grasehotspot.org>”
-
2012-01-22 (Sun, 22 Jan 2012 23:46:47 -0000) - [GRASE-Hotspot] #45: Network settings aren’t always applied - GRASE Trac <tr***c@grasehotspot.org>
- 2012-01-22 (Sun, 22 Jan 2012 23:46:58 -0000) - Re: [GRASE-Hotspot] #45: Network settings aren’t always applied - GRASE Trac <tr***c@grasehotspot.org>
- 2012-01-23 (Mon, 23 Jan 2012 22:28:24 -0000) - Re: [GRASE-Hotspot] #45: Network settings aren’t always applied - GRASE Trac <tr***c@grasehotspot.org>