Somehow alarms get set to year of 1970 on SqueezeNetwork. Seen when debugging issues on SN servers, and result in eating up CPU on servers. These dates now ignored on SN servers, but root cause for these alarms unknown.

Year of alarm probably unix year with value of zero.

Log from SN enclosed. Below says Squeezebox Radio, but not sure if other players can create them too. Also not sure whether alarm works properly in this case or not.

[10-10-09 01:43:48.7608] Slim::Utils::Alarm::scheduleNext (1433) Next alarm is at 1:55:0 2/1/1970
[10-10-09 01:43:48.7609] Slim::Utils::Alarm::scheduleNext (1444) Scheduling alarm
[10-10-09 01:43:48.7612] Slim::Utils::Alarm::sound (508) Alarm triggered for Squeezebox Radio
[10-10-09 01:43:48.7614] Slim::Utils::Alarm::sound (519) Alarm is 1286495328 seconds early/late - ignoring
[10-10-09 01:43:48.7616] Slim::Utils::Alarm::scheduleNext (1400) Asked to schedule next alarm for Squeezebox Radio
[10-10-09 01:43:48.7619] Slim::Utils::Alarm::findNextTime (436) SN time adjusted to wday 6 2:43:0
[10-10-09 01:43:48.7621] Slim::Utils::Alarm::findNextTime (453) Potential next time found: 7:0:0 11/10/2010
[10-10-09 01:43:48.7623] Slim::Utils::Alarm::scheduleNext (1433) Next alarm is at 1:55:0 2/1/1970