Comments
-
Greg Hurrell
Is iTunes not running when you see those messages?
You can avoiding having messages like that printed by lowering your logging threshold (I can explain how to do this), but I might just suppress that message anyway, seeing as it is so harmless and might cause confusion.
-
Bruce
iTunes 7.1.1 was running on Mac OS X 10.4.9.
Would be interested in those instructions to lower logging threshold. Guess large log files might explain a recent unexplained loss in disc space.
-
Greg Hurrell
(In reply to comment #2)
iTunes 7.1.1 was running on Mac OS X 10.4.9.
Would be interested in those instructions to lower logging threshold. Guess large log files might explain a recent unexplained loss in disc space.
The system automatically rotates your log files (starts new files and deletes old ones) so the amount of space taken up by them should be roughly constant over time. In any case, the sizes in question are probably too small to have any noticeable impact (for example, on my system all of my logs added up total to about 75M or 0.04% of my total space).
Info about controlling the logging level is here:
https://wincent.dev/a/products/synergy-advance/help/preferences/advanced/#logging
That documentation applies to version 0.4 of Synergy Advance and you can control the setting in the "Advanced" tab of the preferences:
Synergy Advance can print information to the console (see the "Console" application at "/Applications/Utilities/Console") for the purposes of feedback, diagnostics, debugging and troubleshooting. The verbosity of this logging can be configured using the "Logging level" setting in the advanced preferences. The minimum possible setting is log level 0; at this level Synergy Advance tries to be completely "silent" and not print anything at all to the console (although some error conditions may still arise in which the system libraries, outside of the control of Synergy Advance, print information to the console). The maximum possible setting is log level 10 which is the most verbose setting. The default log level is 1, which means that Synergy Advance will print only a minimum of information to the console, such as error conditions and other events considered as "noteworthy".
In Synergy 0.5b there have been some changes. The preferences UI has been rearranged and there are still more changes to come, so there is no UI-level control for changing the logging level; you have to do it from the terminal. For example, to set the logging level to 0 you would do this in the Terminal (when Synergy Advance is not running):
defaults write com.wincent.SynergyAdvance LogLevel -int 0
Note that the control for this setting will be added back to the UI shortly. This is only a temporary thing during the rearrangement.
The other change to note in 0.5b is documented in the history:
https://wincent.dev/a/products/synergy-advance/history/#0.5b
Specifically:
[Note] Changed the possible range of settings for the "Logging level" advanced preferences; possible values now lie in the range of 0 to 7 (the previous range was 0 to 10) and the default level has been changed from 0 to 5. This change was made to bring Synergy Advance in line with the logging levels specified for the BSD syslog facility in RFC 3164 and mirrored in Apple's ASL ("Apple system log facility"). See the documentation for the "Logging level" setting for more information.
-
Greg Hurrell
(In reply to comment #1)
You can avoiding having messages like that printed by lowering your logging threshold (I can explain how to do this), but I might just suppress that message anyway, seeing as it is so harmless and might cause confusion.
In the current development version (the successor to 0.5b) I've now raised the log-level on those messages to level 6, which means that they won't appear by default (the default log level is 5). In order to see those messages you would need to raise your log level up to 6 or 7. Going to mark this as FIXED/CLOSED.
Add a comment
Comments are now closed for this issue.