Am Dienstag, den 07.10.2008, 12:02 -0400 schrieb rgheck: > Rodolfo Alcazar Portillo wrote: > > could not be a cron issue, that would lead to exactly 1 hour rebooting. > the machine is going to reboot exactly 1 hour after it has successfully > started. Damn right. Didn't noticed that. Anyway, I suppose crontab can't be, because time shifts: # cat /var/log/messages|grep "imklog"|cut -f 1,2,3,4 -d " " Oct 6 04:24:27 Oct 6 04:30:41 Oct 6 05:30:58 Oct 6 06:31:17 Oct 6 07:31:38 Oct 6 08:32:30 Oct 6 09:33:13 Oct 6 10:35:13 Oct 6 11:36:37 Oct 6 12:36:58 Oct 6 13:37:14 Oct 6 14:37:33 Oct 6 15:37:52 Oct 6 16:38:09 Oct 6 17:38:27 Oct 6 18:38:43 Oct 6 19:39:01 Oct 6 20:39:20 Oct 6 21:39:38 Oct 6 22:39:56 Oct 6 23:40:12 Oct 7 00:40:31 Oct 7 01:40:49 Oct 7 02:41:06 Oct 7 03:41:24 Oct 7 04:41:46 Oct 7 05:42:00 Oct 7 06:42:19 Oct 7 07:42:39 Oct 7 08:42:54 Oct 7 09:43:13 As, I said, the problem is solved, just by saving some BIOS changes. My motherboard has a "Wake on alarm" feature, which could be programmed ---------------------------------------------- Rodolfo Alcazar - rodolfo.alcazar@xxxxxxxxxxxx otbits.blogspot.com / counter.li.org: #367962 ---------------------------------------------- "Verrückte und Chefs haben immer Recht." - Aus Venedig -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
