Rare project developers

[Frédéric LOUI <>]

As a user, the main thing I was missing is a way to get external output of a 
process.
Maybe a: display proc <1234> can be useful ?

What I was doing:
Started freeRtr
"show proc external » and check if counters get incremented if not all is 
good if yes, I tried to get the output of the process.

This is where "attach process <1234> » was less comfortable as the output 
could be scrambled and could not exploitable easily.



> Le 3 févr. 2022 à 15:37, Alexander Gall <> a écrit :
> 
> On Thu, 3 Feb 2022 14:06:58 +0100, mc36 <> said:
> 
>> hi,
>> On 2/3/22 13:35, Fr  d  ric LOUI wrote:
>>> 
>>>>> For example, I   m not sure how "reload warm    behaves in Nix. "reload 
>>>>> cold    seem consistent and how hwdet-main / hwdet-all etc. are taken 
>>>>> into consideration.
>>>> should work, and as it turned out that systemd start now everything, i 
>>>> re-added the "clear cef" equivalent stanza: "clear p4lang p4"...
>>> TBH, i liked when this were in control by freeRtr (show process external, 
>>> conf t -> proc 1234 -> stop etc    )
> 
>> 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.
> 
> Another minor reason was that it makes debugging a bit more convenient
> if I want to start the daemons by hand.
> 
> -- 
> Alex