Rare project developers

[Alexander Gall <>]

Hi

I tried to apply the process logging settings to the bffwd and bfswd
processes defined in rtr-hw.txt. However, when I add, for example,

process definition bffwd
  log-console
  exit

from "conf t", it only shows up in "show config-differenecs" and not
in "show running". Also, "write" does not commit the configuration to
rtr-sw.txt.  OTOH, if I add the stanza directly to rtr-sw.txt before I
start freerouter, it will again show up in "config-differences" and
not in "running-config", but with an added "no process definition
bffwd"

rare#show config-differences                                                  
                                                                              
                                                                    
process definition bffwd
 no log-console
 exit
no process definition bffwd

It also appears in "startup-config", but after "write" it's no longer
in rtr-sw.txt.

I guess this has to do with the fact that this is a modification of a
process defined in rtr-hw.txt, but this behaviour is weird and
unexpected.

-- 
Alex

On Thu, 3 Feb 2022 17:24:52 +0100, mc36 <> said:

> partially yeahhh:
> so you can allocate a separate memory log to each process you start,
> and/or could populate the freerouter system-wide logging targets,
> that is, terminal, file, irc, who knows what else... :)
> for now, no separate logfiles generated, for that,
> at the moment you have to configure a matching eem
> and set that's targets separately...
> it obviously have drawbacks both in config and in performance...
> if you could give an example with the positive side effect of having
> separate file backend for each process, it's not a big deal to do so...
> regards,
> cs



> On 2/3/22 17:18, Fr  d  ric LOUI wrote:
>> Brilliant !
>> 
>> So does it mean for example that I can have different log buffer and 
>> different files with lines rotation one for bfswd one for bfwwd and 
>> another one for my external wireless process ? (It is an example of course 
>> as buffed, bfswd is now managed by systemd)
>> 
>> 
>>> Le 3 f  vr. 2022    16:59, mc36 <> a   crit :
>>> 
>>> hi,
>>> after a bit of preparation refactoring (i moved the log buffer 
>>> functionality to a new class to be able to reuse it):
>>> https://github.com/mc36/freeRouter/commit/27eaa686d83c13008d952a39a5a09173f8914bd4
>>> it was straightforward to have the local collections for everything:
>>> https://github.com/mc36/freeRouter/commit/c8a924f95902507b6953edcf94fe7fa1171562d9
>>> so once it's configured, one can issue "sho logg proc p4emu" to see the 
>>> last some lines...
>>> regards,
>>> cs
>>> 
>>> 
>>> 
>>> sid(cfg-scrpt)#show config-differences
>>> script logger
>>> log-collect 123
>>> sequence 1 puts "im here"
>>> exit
>>> 
>>> sid(cfg-scrpt)#
>>> sid(cfg-scrpt)#runnow
>>> info userTest.doer:userTest.java:410 someone from %noVar:remote% hit the 
>>> script
>>> sid(cfg-scrpt)#runnow
>>> info userTest.doer:userTest.java:410 someone from %noVar:remote% hit the 
>>> script
>>> sid(cfg-scrpt)#runnow
>>> info userTest.doer:userTest.java:410 someone from %noVar:remote% hit the 
>>> script
>>> sid(cfg-scrpt)#show logging script logger
>>> im here
>>> im here
>>> im here
>>> 
>>> sid(cfg-scrpt)#
>>> 
>>> 
>>> On 2/3/22 15:51, mc36 wrote:
>>>> not a bad idea, i'll add something asap... :)
>>>> On 2/3/22 15:48, Fr   d   ric LOUI wrote:
>>>>> Maybe a: display proc <1234> can be useful ?
>>