Triode wrote:
> I don't see why this is logging a crash report as its saying the reason
> is receiving a quit signal - I would expect the application to close
> when it sees this. Perhaps someone more familiar with OSX can comment?
Well no - any *nix uses the SIGQUIT signal to cause a "core" dump. It
was often generated interactively buy a developer typing ctrl-\ at the
foreground process to get a dump for debugging.
SIGINT is the signal that can be generated by ctrl-C at the keyboard and
normally causes a clean termination of a process - but it can be
"caught" by the receiving process to let it do some cleaning up before
exiting.
I turned logging to DEBUG for spotifyd and stopped LMS again. Nothing in
the spotify log, but the server log said:
[12-08-22 10:42:35.7588] Plugins::Spotify::Spotifyd::shutdownD (158)
killing spotifyd
In your SpotifyD.pm you have:
sub shutdownD {
my $class = shift;
if ($spotifydChecker) {
Slim::Utils::Timers::killSpecific($spotifydChecker);
$spotifydChecker = undef;
}
if ($spotifyd && $spotifyd->alive) {
$log->info("killing spotifyd");
$spotifyd->die;
}
}
Which presumably generated the log message. What is the effect of
$spotifyd->die;?
------------------------------------------------------------------------
nonnoroger's Profile: http://forums.slimdevices.com/member.php?userid=35581
View this thread: http://forums.slimdevices.com/showthread.php?t=79706
_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/plugins
