Bug 4598 – Better CLI scanner access

Bug 4598 - Better CLI scanner access

Summary:

Better CLI scanner access

Status:	CLOSED FIXED

Product:	Logitech Media Server
Classification:	Unclassified
Component:	CLI
Version:	6.5b3
Platform:	PC All

Importance:	P2 enhancement (vote)
Target Milestone:	Future
Assigned To:	Chris Owens

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2006-12-14 08:08 UTC by Dr Lovegrove
Modified:	2008-12-15 13:07 UTC (History)
CC List:	1 user (show)

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Dr Lovegrove 2006-12-14 08:08:43 UTC

Be nice to have more control over the scanner from the CLI. Currently we can tell if a scan's in progress and initiate a whole new scan, but it would be very useful to know the progress of the current scan, and to be able to specify individual folders to rescan.

Comment 1 Chris Owens 2007-02-12 14:56:16 UTC

cc'ing Fred for any comments

Comment 2 Fred 2007-02-12 16:06:13 UTC

Progress is certainly imaginable now this is in the web interface. 
Scan a particular folder: the server scanning code is not ready for that today, so this is more a general enhancement than a CLI enhancement. True, scanning a particular folder would be most interresting as part of some automated workflow.

Comment 3 Fred 2007-05-19 14:20:10 UTC

Done in r12055. Can be closed.

Comment 4 Fred 2007-05-19 14:22:42 UTC

Scanning a folder is currently somewhat supported by Browse Music Folder (SS imports into the DB any new folder/song), for which there will be CLI access soon.

Comment 5 Fred 2007-05-26 03:48:54 UTC

all done. musicfolder can browse a folder by URL and it will scan it.

Comment 6 KDF 2007-05-26 11:37:49 UTC

change 12055
marking as fixed. reopen if there are issues.

Comment 7 James Richardson 2008-12-15 13:07:47 UTC

This bug appears to have been fixed in the latest release!

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

Make sure to include the version number of the software you are seeing the error with.