I could not find any documentation for these 3 parameters which are available for most CLI print commands.
But I have the feeling, depending on the section where the print command is used, they act different every time.
I always thought “follow-only” may be something like “tail -f” on linux.
But this does not output anything besides these separator line and the hint “hit spacebar to add a separator”.
Same goes for the other arguments. I simply do not know what they should do, because for me they do something different I would expect.
Neither follow nor follow-only nor follow-strict are described. I would like to know the conceptual differences so I can distinguish when one makes more sense.
Seems like. But if this is really the equivalent, then “follow-strict” is probably the most inappropriate name of all time. There is no follow. Nothing strict also.
Indeed, follow-strict does not add any thing different than print already do. It might be interesting to replace it with a option to limited the number of lines shown, beginning from last.
follow-last=10 → shows the last ten lines (.id) from the otherwise printed text.
edit: then time could be also a way to select for items that also store times
follow-last=10s → shows the last lines that where written in the last 10 seconds
When using the option interval you can monitor but you don’t can’t select how many. Time is possible if you set the refresh time. And then filter out lines already seen. Easier is then to use follow-only and loop that every n-time.
You can kinda cheat by using another “memory store” for the log with only 10 lines. I do to keep a readable log longer term, but still show debug-ish things. Not quite what you’re looking for however — I’m not sure you can just print the last 10 lines, easily that is.
/system logging add action=short topics=!debug memory-lines=10
/log print where buffer=short