Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×
The Claris Museum: The Vault of FileMaker Antiquities at Claris Engage 2025! ×

This topic is 4448 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

Is there any way to stop, or restrict the log file.

I have a plugin created with ScriptMaster with a that is called about every 2 secs, 24 hours a day. This is creating a huge log file, and I think possibly causing the routine to hang occasionally - the last noticeable time the log file was over 1Gb. Tricky to open in NotePad!

If there was a command to set the log file to record only errors rather than routine calls it would be a great help. Or a way to start a new log file without restarting FileMaker as this is not an option.

Thanks

Tim

  • 2 weeks later...
  • 2 weeks later...
Posted

Hey Tim,

 

There is actually a way to increase/reduce the logging level of the log files being created by the 360Works plug-ins. You will need to edit the logging.properties file by adding something similar to:

 

com.prosc.beanshell.level = SEVERE

(where com.prosc.beanshell is the Java package for ScriptMaster) at the bottom of the properties file. The above would limit the logged messages to the SEVERE level, which would reduce your log file by displaying only the errors that are marked as severe. The default location of the logging.properties file is located at:

 

"lib/logging.properties", inside the JRE directory.

 

I hope this helps.

 

Signed,

This topic is 4448 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.