And, sorry to respond to my own post, but more info may help:
1) the desktop software doesn't create this file, as I've tested that
2) I was at a hotel when the log file grew. I don't know if this is a contributing factor, but I do know that every 24 hours the hotel would redirect and make me acknowledge usage rights/expectations. I probably did have the sling player running during one of these 'cutouts', where they would redirect my browsing page to their page...so this file could have been logging attempts to connect to the slingbox.com, then getting the redirect...causing a loop.
In either case, I stand by 25 G of logs is excessive and methods to watch this and 'roll it' would be good, provided it only kept one or two of the files, not as many as possible.
I just discovered this, too, as my hard drive was nearly full (after having about 30GB available one day earlier). This happened after watching a hockey game last night at my son's house. We did have to re-log back in when there was a "problem" with the Internet connection. That's the only thing that happened out of the ordinary. I just deleted the file this morning, but it was 25GB.
You could create a symbolic link to /dev/null via the terminal app.
Open up a terminal and type man ln to see the options.
Off the top of my head its :-
ln -s DebugLog_1.txt /dev/null
ln -s SlingSS_log.txt /dev/null
Oops had the command round the wrong way round
ln -s /dev/null DebugLog_1.txt
ln -s /dev/null SlingSS_log.txt
Should look something like this when linked :-
macbookpro:Logs AndyK$ pwd
macbookpro:Logs AndyK$ ls -al
drwxr-xr-x@ 6 AndyK staff 204 24 Oct 21:08 .
drwxr-xr-x 7 AndyK staff 238 19 Oct 21:00 ..
-rw-r--r--@ 1 AndyK staff 6148 24 Oct 21:04 .DS_Store
lrwxr-xr-x 1 AndyK staff 9 24 Oct 21:07 DebugLog_1.txt -> /dev/null
lrwxr-xr-x 1 AndyK staff 9 24 Oct 21:07 DebugLog_2.txt -> /dev/null
lrwxr-xr-x 1 AndyK staff 9 24 Oct 21:08 SlingSS_Log.txt -> /dev/null
You need to change directory in the terminal app to ~/Library/Application Support/SlingMedia/Logs
its a shame that the log files aren't pruned to a certain size by the plugin.
This will prevent any log file being written and the two files will remain a size of 0
Check out using Fluid rather than Safari, it looks way better.
Point the URL to http://watch.slingbox.com/watch/sideview?playerType= and set the UserAgent to Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_8; en-us) AppleWebKit/531.21.8 (KHTML, like Gecko) Version/4.0.4 Safari/531.21.10
Looks much tider :-
You can use an App called Moom to force the window to reize the window to what ever you prefer.
Making the log file go to /dev/null might fix them symptom but does not point to the source of the never-ending logfile disease.
I woke up to a nearly full 1 TERABYTE startup drive on my iMac (Lion, OSX 10.7.2) this morning, and traced the problem to a 679 GIGABYTE Slingbox log file, specifically, slingSS_log.txt
I accessed both of the two slingboxes I connect to yesterday from this Mac, but logged out of them both when finished, and closed the browser used for the connection more than 24 hours ago.
Does anyone have a good answer to WHY a log file will continue to be generated continusously when the app is not in use, to the point where said logfile may fill the system startup disk and render the Mac unusable?
(Before you ask, I deleted the file in question and emtied the trash to avoid crashing my system as it grew.)