On Tue, Jul 9, 2013 at 2:19 PM, John Crispin wrote:
> On 09/07/13 14:22, Helmut Schaa wrote:
>>
>> On Tue, Jul 9, 2013 at 2:14 PM, John Crispin wrote:
>>>
>>> On 09/07/13 14:18, Helmut Schaa wrote:
How is procd supposed to get started? Only as init replacement?
>>>
>>>
>>> Hi,
>>>
>>>
On 09/07/13 14:22, Helmut Schaa wrote:
On Tue, Jul 9, 2013 at 2:14 PM, John Crispin wrote:
On 09/07/13 14:18, Helmut Schaa wrote:
How is procd supposed to get started? Only as init replacement?
Hi,
From state.c:
case STATE_INIT:
LOG("- init -\n");
On Tue, Jul 9, 2013 at 2:14 PM, John Crispin wrote:
> On 09/07/13 14:18, Helmut Schaa wrote:
>> How is procd supposed to get started? Only as init replacement?
>
> Hi,
>
> From state.c:
> case STATE_INIT:
> LOG("- init -\n");
> log_init();
>
On Tue, Jul 9, 2013 at 2:18 PM, Helmut Schaa
wrote:
> How is procd supposed to get started? Only as init replacement?
Hmm, ubusd should still get started from state_enter in STATE_INIT :)
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
ht
On 09/07/13 14:18, Helmut Schaa wrote:
On Tue, Jul 9, 2013 at 1:59 PM, John Crispin wrote:
there was a bug in the delay timer, that tried to reconnect to ubus every
minute. ... maybe you can add some debug code to it and see whats wrong. its
inside ubus.c in the procd source
Hmm, there is no
On Tue, Jul 9, 2013 at 1:59 PM, John Crispin wrote:
> there was a bug in the delay timer, that tried to reconnect to ubus every
> minute. ... maybe you can add some debug code to it and see whats wrong. its
> inside ubus.c in the procd source
Hmm, there is no procd init file anymore?
However, pro
On 09/07/13 14:03, Helmut Schaa wrote:
Hey John,
On Tue, Jul 9, 2013 at 1:51 PM, John Crispin wrote:
does this happen on latest trunk ?
Pulled yesterday.
Just found out that procd should start ubus, not sure yet whats happening ...
Helmut
hi helmut,
there was a bug in the delay timer, tha
Hey John,
On Tue, Jul 9, 2013 at 1:51 PM, John Crispin wrote:
> does this happen on latest trunk ?
Pulled yesterday.
Just found out that procd should start ubus, not sure yet whats happening ...
Helmut
___
openwrt-devel mailing list
openwrt-devel@lists
On 09/07/13 13:58, Peter Wagner wrote:
This patch fixes logread and now appends to files instead of writting to the
beginning the specified logfile.
It also sets the access rights to 0600.
Signed-off-by: Peter Wagner
Thanks, i will add this to the git tree in the next couple of hours
This patch fixes logread and now appends to files instead of writting to the
beginning the specified logfile.
It also sets the access rights to 0600.
Signed-off-by: Peter Wagner diff --git a/logread.c b/logread.c
index fc1d0ce..77a810b 100644
--- a/logread.c
+++ b/logread.c
@@ -116,7 +116,7 @@ s
On 09/07/13 13:55, Helmut Schaa wrote:
On Sun, Jun 23, 2013 at 4:54 AM, Remzi AKYÜZ wrote:
I tried to use openwrt r36979 but i got this error message "Failed to
connect to ubus".
Same here, culprit seems to be the following commit:
commit 4f6a8df9b3f2f02c3cdcc0719d9e6ef7280eac51
Author: cy
On Sun, Jun 23, 2013 at 4:54 AM, Remzi AKYÜZ wrote:
> I tried to use openwrt r36979 but i got this error message "Failed to
> connect to ubus".
Same here, culprit seems to be the following commit:
commit 4f6a8df9b3f2f02c3cdcc0719d9e6ef7280eac51
Author: cyrus
Date: Mon Jun 24 12:38:30 2013 +
Hello everyone,
I accidentally added a wrong path in the package I am working on - the name of
the file does not end with .patch and is not the result of a diff - and I
observed this behaviour:
make package/mypackage/{clean,prepare,compile} QUILT=1
I got an error because that file is completel
13 matches
Mail list logo
