cliveb;533363 Wrote: > Thanks to everyone for their suggestions (guesses?) > > I was hoping that what needs to be done is to switch on the appropriate > debug logging. What I'm unclear about is how that is done. Do I just do > it via the Squeezecenter web interface (Settings > Advanced > Logging)? > And if so, which ones would people suggest might be worth switching on? > Does Squeezecenter need to be restarted after changing a log level? > > Mind you, they are all set to "error" anyway, and presumably a segfault > is at least an error - but I see nothing in the logs corresponding to > the times of the segfaults. My guess is that the segfault just kills > the process, and it never gets a chance to write a log entry. > > It's obvious from dmesg that whatever is crashing has a different > process ID each time. Anyone here know what daily procedures > Squeezecenter performs that it does by forking? That would at least > narrow it down. I think you are going to have to bite the bullet and set debugging level to DEBUG - very verbose, but it will trap things happening at the same time as your seg fault. I'd start with the server and scanner set...
-- Phil Leigh You want to see the signal path BEFORE it gets onto a CD/vinyl...it ain't what you'd call minimal... Touch(wired/XP) - TACT 2.2X (Linear PSU) + Good Vibrations S/W - MF Triplethreat(Audiocom full mods) - Linn 5103 - Aktiv 5.1 system (6x LK140's, ESPEK/TRIKAN/KATAN/SEIZMIK 10.5), Townsend Supertweeters, Blue Jeans Digital,Kimber Speaker & Chord Interconnect cables Kitchen Boom, Outdoors: SB Radio ------------------------------------------------------------------------ Phil Leigh's Profile: http://forums.slimdevices.com/member.php?userid=85 View this thread: http://forums.slimdevices.com/showthread.php?t=77160 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/discuss
