Skip navigation

How to stop QuickTime Streaming messages in secure.log?

446 Views 4 Replies Latest reply: Jan 26, 2013 1:53 PM by marc herman RSS
marc herman Level 1 Level 1 (30 points)
Currently Being Moderated
Jan 26, 2013 1:49 AM

The secure.log of the server is flooded with these kind of messages:

 

Jan 25 12:13:08 server com.apple.SecurityServer[41]: Succeeded authorizing right 'com.apple.server.admin.streaming' by client '/usr/sbin/QuickTimeStreamingServer' for authorization created by '/System/Library/CoreServices/ServerManagerDaemon.bundle'

Jan 25 12:13:40: --- last message repeated 13 times ---

Jan 25 12:13:40 server com.apple.SecurityServer[41]: Succeeded authorizing right 'com.apple.server.admin.streaming' by client '/usr/sbin/QuickTimeStreamingServer' for authorization created by '/System/Library/CoreServices/ServerManagerDaemon.bundle'

Jan 25 12:15:03: --- last message repeated 7 times ---

Jan 25 12:15:03 server com.apple.SecurityServer[41]: Succeeded authorizing right 'com.apple.server.admin.streaming' by client '/usr/sbin/QuickTimeStreamingServer' for authorization created by '/System/Library/CoreServices/ServerManagerDaemon.bundle'

Jan 25 12:15:34: --- last message repeated 3 times ---

 

I have tried to adjust the idle time setting in /Library/Preferences/com.apple.servermgrd.plist to 300, the supposed Maximum above which idle time defaults to 60 seconds. In my experience this initially works after which the flooding starts all over. The default interval is also a lot smaller than 60 secs.

 

How to effectively eliminate these messages apart from disabling QuickTime Streaming all together?

Mac mini, Mac OS X (10.6.8), Server
  • MrHoffman Level 6 Level 6 (11,700 points)

    You've provided a very explaination of the what you're looking at and what you've tried, but is there a particular reason why you're looking to suppress these messages?  If it's because those log entries are overruning the blasted mail-slot-sized log windows available in the Server Admin.app tool, it's usually easier to review or grep or otherwise directly process the raw logs in the /var/log directory.

  • MrHoffman Level 6 Level 6 (11,700 points)

    I would.  (Ignore it.)  OS X logging has long had this misfeature; various versions of applications have been far too chatty, others have log ominous messages that are harmless, and there's the occasional innocuous-nasty message logged.  

     

    If this particular message bugs you — I have several similar "favorites" in my own logs — add it onto a grep --invert-match pattern or such, and filter it out of the logs before you review them.  When you're running OS X or another Unix box in production, message filters based on grep or similar are used to reduce the chatter, and also to flag the nasty messages.

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.