Rare project developers

[mc36 <>]

hi,

On 2/3/22 15:37, Alexander Gall wrote:
> > with this change
> > https://github.com/mc36/freeRouter/commit/42ce76397ceaafa774b22f9323d3e199aa2fd67d
> > from now, one can have the console logs from the spawned things, for example 
> > is the external processes...
> > it have the positive side effect that it appears on the "term mon" sessions 
> > or goes to the configured places like file/syslog/irc/whatever...
> > i added this because you mentioned yesterday that it was the main driver of 
> > moving out the swtichd management from freerouter...
> > was there any other reasons?
>
> That was the main reason. With this new method, I suppose we can use
> "term mon" and still log to a file at the same time? Can we have
> processes log to separate files or will it all end up in the same?  I
> suppose we'll then also have to use logrotate to manage the file.
so freerouter does minic the cisco logging stuff...
obviously all the active log targets get the messages....
and you can easily separate the logs onboard, with the eem stuff...
(but it's usually done at the syslog target's backend...)
and have some extra: for example the file backed can be configured to 
rotate...
but it's not a full logrorate, just after a given size/time/whatever you set,
moves the current to old, and starts a fresh one... this way one can check
regularly the old from a script and compress/archive/whatever when it 
appears...

> Another minor reason was that it makes debugging a bit more convenient
> if I want to start the daemons by hand.

so from sysadmin perspective the journalctl is the convenient and usual,
but from netadmin perspective i see the freerouter internal logging
more convenient and usual...

regards,
cs