Re: symon (symux?): io(...) don't work with -current

2010-10-21 Thread Anton Maksimenkov
2010/10/18 Stuart Henderson : > Two methods to handle this come to mine, we could simply skip > a : and any text up to the next "," or terminating NUL, alternatively > we could add uid support without too much trouble, the diff below > does this and makes a few porting changes: works for me. -- a

Re: symon (symux?): io(...) don't work with -current

2010-10-18 Thread Stuart Henderson
On 2010/10/15 14:01, Anton Maksimenkov wrote: > 2010/10/14 Anton Maksimenkov : > > I used symon on my servers (4.5, 4.7, current) and one symux. symux > > runs on -current. > > As you can see, there is "io" from core (4.7), but no "io" from db1 > > (current) and no "io" from mx (current, running sy

Re: symon (symux?): io(...) don't work with -current

2010-10-15 Thread Anton Maksimenkov
2010/10/14 Anton Maksimenkov : > I used symon on my servers (4.5, 4.7, current) and one symux. symux > runs on -current. > As you can see, there is "io" from core (4.7), but no "io" from db1 > (current) and no "io" from mx (current, running symux). This is a simple patch which resolves my problem:

symon (symux?): io(...) don't work with -current

2010-10-14 Thread Anton Maksimenkov
Hello. I used symon on my servers (4.5, 4.7, current) and one symux. symux runs on -current. On all servers symon started without errors and debug looks like this symon version 2.82 program id=25205 debug: symon packet size=452 sending packets to udp A.B.C.D 2100 (5s) started module if(lo0) start