Hi,
this is already fixed in trunk. The uhttpd stderr is relayed to syslog
there.
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
today I was searching for a non-running uhttpd and
recognized, that there are no error messages anymore
if something goes wrong. in 62ff68fb / r38023
# procd: convert various packages to procd style init.d scripts
# Signed-off-by: John Crispin blo...@openwrt.org
the debug-output was commented
* Jo-Philipp Wich j...@openwrt.org [11.05.2015 10:29]:
this is already fixed in trunk. The uhttpd stderr is relayed to syslog
there.
thank you - i see:
this is not very intuitive. can this be send to console
when user is interactive? (like: loggger -s message)
bye, bastian
* Jo-Philipp Wich j...@openwrt.org [11.05.2015 11:47]:
this is not very intuitive. can this be send to console
when user is interactive? (like: loggger -s message)
Not easily as it is procd logging the services stderr. One can implement
a test or debug start action though which would
it think thats too special - there should be a generic way to
get direct feedback on the commandline when something fails without
doing magic. what if we e.g. 'export INTERACTIVE=1' via /etc/profile
so procd / a called script is aware of this?
Whats too special with /etc/init.d/$SERVICE debug
Hi.
thank you - i see:
this is not very intuitive. can this be send to console
when user is interactive? (like: loggger -s message)
Not easily as it is procd logging the services stderr. One can implement
a test or debug start action though which would calculate the
commandline and start the
On 2015-05-11 00:26, Luka Perkov wrote:
Signed-off-by: Luka Perkov l...@openwrt.org
---
= changes in v2:
Use new libubox base64 provided API.
file.c | 118
+++--
1 file changed, 107 insertions(+), 11 deletions(-)
diff
* Jo-Philipp Wich j...@openwrt.org [11.05.2015 12:34]:
it think thats too special - there should be a generic way to
get direct feedback on the commandline when something fails without
doing magic. what if we e.g. 'export INTERACTIVE=1' via /etc/profile
so procd / a called script is aware
---
package/kernel/w1-gpio-custom/src/w1-gpio-custom.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/package/kernel/w1-gpio-custom/src/w1-gpio-custom.c
b/package/kernel/w1-gpio-custom/src/w1-gpio-custom.c
index fc2f842..2018f58 100644
---
Am 09.05.2015 um 18:26 schrieb Chris Blake:
This patch is to add support for the Meraki MR12 and MR16 Access Points.
Currently everything is working, minus the 2nd NIC interface on the MR12
which is built into the SoC.
Signed-off-by: Chris R Blake chrisrblak...@gmail.com
Your patch is line
On Mon, May 11, 2015 at 9:17 PM, Steven Barth cy...@openwrt.org wrote:
Fine with me in principle, howeverI find the name force_ps to be
misleading since the option does not override or enforce anything. Maybe
default_ps would be a more suitable name?
OK will change the name into default_ps in
The PCIe bus seems to require a hack/workaround when PCI is enabled as
well. Unfortunately this is guarded by an CONFIG_IFX_PCI ifdef, which is
only defined in lantiq's BSP code. The config symbol for the upstream
lantiq PCI driver is CONFIG_PCI_LANTIQ.
Signed-off-by: Martin Blumenstingl
Fine with me in principle, howeverI find the name force_ps to be
misleading since the option does not override or enforce anything. Maybe
default_ps would be a more suitable name?
Cheers,
Steven
On 11.05.2015 18:30, Hans Dedecker wrote:
Default packet steering behavior can be configured
Signed-off-by: Luka Perkov l...@openwrt.org
---
file.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/file.c b/file.c
index fe1bc39..64e7c28 100644
--- a/file.c
+++ b/file.c
@@ -247,7 +247,7 @@ rpc_file_read(struct ubus_context *ctx, struct ubus_object
*obj,
Hi Felix,
On Mon, May 11, 2015 at 11:36:46AM +0200, Felix Fietkau wrote:
On 2015-05-11 00:26, Luka Perkov wrote:
Signed-off-by: Luka Perkov l...@openwrt.org
---
= changes in v2:
Use new libubox base64 provided API.
file.c | 118
On 2015-05-11 23:26, Luka Perkov wrote:
Hi Felix,
On Mon, May 11, 2015 at 11:36:46AM +0200, Felix Fietkau wrote:
On 2015-05-11 00:26, Luka Perkov wrote:
Signed-off-by: Luka Perkov l...@openwrt.org
---
= changes in v2:
Use new libubox base64 provided API.
file.c | 118
This patch adds the pll_1000 value for eth0 interface. This makes the Rocket M
XW image compatible with other Ubiquiti devices with similar hardware with a
Gigabit Ethernet port.
---
.../ar71xx/patches-3.18/903-MIPS-ath79-ubnt-rocket-m-xw-support.patch | 3 ++-
1 file changed, 2 insertions(+), 1
This patch adds the pll_1000 value for eth0 interface. This makes the Rocket M
XW image compatible with other Ubiquiti devices with similar hardware with a
Gigabit Ethernet port.
Signed-off-by: Roger Pueyo Centelles roger.pu...@guifi.net
---
Signed-off-by: Luka Perkov l...@openwrt.org
---
= changes in v2:
Use new libubox base64 provided API.
= changes in v3:
* optimize base64 related code in read and write callback
file.c | 90 ++
1 file changed, 79 insertions(+), 11
Signed-off-by: Luka Perkov l...@openwrt.org
---
= changes in v2:
Return umask() to previous value after temporary changing it.
file.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/file.c b/file.c
index d39dccb..fe1bc39 100644
--- a/file.c
+++ b/file.c
@@ -93,6
Signed-off-by: Luka Perkov l...@openwrt.org
---
= changes in v2:
Use new libubox base64 provided API.
= changes in v3:
* optimize base64 related code in read and write callback
= changes in v4:
* tweak if block in file read function
file.c | 90
This patch is to add support for the Meraki MR12 and MR16 Access Points.
Currently everything is working, minus the 2nd NIC interface on the MR12
which is built into the SoC.
Signed-off-by: Chris R Blake chrisrblake93 at gmail.com
--
diff --git a/target/linux/ar71xx/base-files/etc/diag.sh
Make sure brctl build uses appropriate defines (_FILE_OFFSET_BITS) that match
uClibc settings.
Without this patch running brctl leads to 'unresolved alphasort symbol' message.
Signed-off-by: Nikolay Martynov mar.ko...@gmail.com
---
net/bridge-utils/Makefile | 2 ++
1 file changed, 2
Default packet steering behavior can be configured via the parameter force_ps
in the global section; the default value is true to keep backwards
compatibility.
Device packet steering (rps/xps) config can still be used to override the
default behavior.
This allows you to disable packet steering
On 03/21/2015 10:16 AM, Stefan Rompf wrote:
Hi Sergey,
You should be a wizard to reveal hw protocol without touching hw :)
I cannot say 'Mischief managed!' by now, but it's slowly making progress ;-)
Unlikely that iwconfig changes something directly, I would bet on the
driver.
25 matches
Mail list logo
