Scribe Scribe v3.2.3 [2025-Aug-24] - Entware syslog-ng and logrotate installer for Asuswrt-Merlin

[John Fitzgerald]

I'm curious if it was intentional to list the OSR link to uiScribe and not scribe in the title?

View attachment 67567

I’ll bite.
It was intentional.
How would you like your efforts acknowledged?

I have no skin in the game here but if the question is meant to clear up a misunderstanding more easily then please let your feelings be known here.

I’m sure no offense was meant.

 

[dave14305]

I’ll bite.
It was intentional.
How would you like your efforts acknowledged?

I have no skin in the game here but if the question is meant to clear up a misunderstanding more easily then please let your feelings be known here.

I’m sure no offense was meant.

I think you’ve overlooked the obvious error that the scribe script header now incorrectly points to the uiScribe repository url. It has nothing to do with attribution or ownership. scribe and uiScribe are different repositories on github.

 

[Martinski]

I'm curious if it was intentional to list the OSR link to uiScribe and not scribe in the title?

View attachment 67567

Good eye!! That's indeed a mistake. It's fixed now. Thanks for catching it.

For clarity, the error was introduced when we migrated Scribe's original repository to the AMTM-OSR repo, so it's been there since our initial v3.2.2 release. It was simple human error - nothing else and nothing more.

 

[Martinski]

I had a minor glitch with the update on my GT-BE98 Pro. scribe lost track of the syslog.log location. Simple fix was to re-detect it within scribe utilities (su. followed by rd. in the scribe menu).

Hmmm... I wonder how Scribe loses track of the syslog.log location. In the script, there's code that figures out the location of the original syslog.log file and then stores that information in a config file. That location would (and should) not change on the same router running the same F/W, so it's a very odd scenario. Fortunately, @cmkelley had the foresight to have a mechanism in place to "re-detect" the location (via the utility menu options you described) when things go awry.

Can you elaborate on the outward signs you notice when the problem occurred?
Did you happen to see the wrong or missing entry from the "Show scribe status" menu option?

I'm just trying to get a better understanding of the problem.

Thanks.

 

[visortgw]

Hmmm... I wonder how Scribe loses track of the syslog.log location. In the script, there's code that figures out the location of the original syslog.log file and then stores that information in a config file. That location would (and should) not change on the same router running the same F/W, so it's a very odd scenario. Fortunately, @cmkelley had the foresight to have a mechanism in place to "re-detect" the location (via the utility menu options you described) when things go awry.

Can you elaborate on the outward signs you notice when the problem occurred?
Did you happen to see the wrong or missing entry from the "Show scribe status" menu option?

View attachment 67575

I'm just trying to get a better understanding of the problem.

Thanks.

Yes, the missing entry appears in the "Show scribe status" menu. I initially saw it during the update itself.