[abcde] Re: cddb and speed

[Robert Woodcock <rcw@debian.org>]

On Wed, Mar 14, 2001 at 08:56:00PM -0700, Mark C. Smith wrote:
> Hey, 
> Got a couple of questions and maybe a  (o.k) solution for speed.
> I'm burning a cd that's getting a lot of SCSI/ATAPI transport 
> errors so it's taking it's sweet time.  Anyway, I noticed that
> my system was crawling through this, so I killed syslogd for 
> the time being.  It definately improved the response speed, but
> if this is a stupid thing to do, please let me know.

The only way this could possibly help is if your syslogd is really being
bogged down by SCSI kernel errors (the kernel would be the only thing
logging these messages). If that's the case, you might want to adjust your
kernel logging level in syslogd.conf or perhaps force async logging by
putting a - before the filename.

Some SCSI devices do not play nice in situations like these. Compaq PD 650
drives in particular seem to eat system CPU alive.

You may just want to tell cdparanoia to stop retrying when it hits a bad
spot - the cdparanoia manpage explains the -X, -Y, and -Z options better
than I can.

> I definately
> plan on bringing syslog back up when I'm through w/ the cd.
> Also, cddb-tool grabs a huge error from the site (www.gracenote.com
> I think) about the program not being about to access the database.
> It then uses the error for the tracks on my cd.  Anyone else had
> any problems w/ this?  Thanks.

Gracenote hates you. You use some rogue command-line program to get your
CDDB data, you're not giving up your privacy so you can use CDDB2, and
you're not generating any advertising revenue for them.

Use a CDDB server that's run by people who don't hate you. Use FreeDB.

See http://idea.lly.org/~rcw/abcde/list/current/msg00002.html
-- 
Robert Woodcock - rcw@debian.org
"* We used to try various strange things. Let's not."
	-- seen in linux/fs/buffer.c

To unsubscribe: echo unsubscribe | mail abcde-request@whimsica.lly.org