Bug 13197 - runtime parameter --help needs to be updated (logdir missing)
: runtime parameter --help needs to be updated (logdir missing)
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Scanner
: 7.4.0
: PC Windows XP
: P4 trivial (vote)
: 7.4.0
Assigned To: Michael Herger
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-08-02 00:30 UTC by Philip Meyer
Modified: 2009-10-05 14:25 UTC (History)
3 users (show)

See Also:
Category: Bug


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philip Meyer 2009-08-02 00:30:31 UTC
I start my server with: slimserver.pl --prefsdir "D:\Squeezebox Server\trunk\Prefs" --logfile "D:\Squeezebox Server\trunk\Logs\Log.txt"

When I start a scan, the scanner runs separately, and logs to C:\Documents and Settings\All Users\Application Data\Squeezebox\Logs\scanner.log.

Took me a while to find the log; I don't appear to have any way to control where the log is created (not good when I am running several versions of the server).

Any chance that we could have a --logdir (instead of --logfile), or assume that scanner.txt should be written to the path that the logfile is written to?
Comment 1 Jim McAtee 2009-08-02 15:54:53 UTC
We do now have --logdir. :)  For more than two years, ever since SC 7.0 or whenever the scanner began logging to a file separate from the server log.  Does --logfile still do anything?
Comment 2 Jim McAtee 2009-08-02 16:05:02 UTC
Wow... I just entered the following on Windows: >squeezesvr.exe --help and only found

--logfile => Specify a file for error logging.  Specify 'syslog' to log to syslog.

Apparently --logdir has never been documented in this Help.
Comment 3 Philip Meyer 2009-08-03 00:08:06 UTC
I've never heard of --logdir.  I just tried it, and it had no effect.
Comment 4 Jim McAtee 2009-08-03 00:37:04 UTC
Here's an early mention of it in the forums:

http://forums.slimdevices.com/showthread.php?p=168450#post168450

I've been using it for quite a while, and all three logs are created in the directory.

"C:\Program Files\Squeezebox Server 7.4 Trunk\server\slimserver.pl" --playeraddr 192.168.9.11 --cliaddr 192.168.9.11 --streamaddr 192.168.9.11 --httpaddr 192.168.9.11 --prefsdir D:\slim\11\prefs --cachedir D:\slim\11\cache --logdir D:\Slim\11\logs
Comment 5 James Richardson 2009-08-03 07:44:48 UTC
Who's responsible for adding this to the help --text?
Comment 6 Chris Owens 2009-08-03 09:39:55 UTC
Michael says looking at the code this should work.

QA to reproduce.  Michael should probably be responsible for adding the help text, when we're done.
Comment 7 Philip Meyer 2009-08-03 15:09:28 UTC
--logdir "D:\Squeezebox Server\trunk\Logs" doesn't work for me.

--logdir "D:\Temp" does, so could it be that it doesn't support spaces in the path name (even though I protected it with quotes?)


NB. --prefsdir "D:\Squeezebox Server\trunk\Prefs" works okay.
Comment 8 Philip Meyer 2009-08-03 15:21:26 UTC
Sorry, ignore me.  It does work - I hadn't noticed that the file that gets created is server.log, whereas I had a link to tail the log.txt.

Doh.
Comment 9 Michael Herger 2009-08-03 21:55:12 UTC
Thanks for your feedback. Changing the subject.
Comment 10 Philip Meyer 2009-08-04 01:07:42 UTC
When I start a new scan, it overwrites the previous scanner.log file, rather than append to it.  Is that intentional behaviour?  The server.log is always appended to.
Comment 11 Jim McAtee 2009-08-04 01:16:37 UTC
(In reply to comment #10)
> When I start a new scan, it overwrites the previous scanner.log file, rather
> than append to it.  Is that intentional behaviour?  The server.log is always
> appended to.

I seem to recall that behavior was added to the noweb-sqlite branch, maybe because of the verbose scanner logging (one line logged for every file that is scanned).  Seems to me that at a minimum one prior scanner log should be preserved.  Another bug to file?
Comment 12 Michael Herger 2009-08-04 01:25:41 UTC
> When I start a new scan, it overwrites the previous scanner.log file,  
> rather
> than append to it.  Is that intentional behaviour?  The server.log is  
> always appended to.

Yes, it has been this way for many weeks already.
Comment 13 Michael Herger 2009-08-05 00:09:10 UTC
 == Automatic comment from SVN commit #28063 to Repository: slim ==
https://svn.slimdevices.com/slim?view=revision&revision=28063

Fixed Bug: 13197
Description: document --logdir in slimserver.pl


 == Modified 1 files total ==
7.4/trunk/server/slimserver.pl
Comment 14 James Richardson 2009-10-05 14:25:59 UTC
This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server!
    * SqueezeCenter: 28672
    * Squeezebox 2 and 3: 130
    * Transporter: 80
    * Receiver: 65
    * Boom: 50
    * Controller: 7790
    * Radio: 7790  

Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes

If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.