Michael Kelly, le lun. 02 mars 2026 14:37:35 +0000, a ecrit:
> On 02/03/2026 13:40, Samuel Thibault wrote:
> > > Is there a log that I can access that shows the sequence of builds that 
> > > are
> > > run on the buildd?
> > https://buildd.debian.org/status/recent.php?a=hurd-amd64&suite=sid
> > shows it
> 
> This is very helpful. Is it possible to determine when boralus was rebooted?

I don't think these logs can provide that information. I can easily see
the cronjob, though:

# zgrep -i @reboot syslog.7.gz syslog.6.gz syslog.5.gz syslog.4.gz syslog.3.gz 
syslog.2.gz syslog.1 syslog
Feb 21 18:06:07 boralus cron[623]: (CRON) INFO (Running @reboot jobs)
Feb 21 20:10:38 boralus cron[623]: (CRON) INFO (Running @reboot jobs)
Feb 21 23:17:40 boralus cron[623]: (CRON) INFO (Running @reboot jobs)
Feb 22 01:15:35 boralus cron[625]: (CRON) INFO (Running @reboot jobs)
Feb 22 09:55:48 boralus cron[625]: (CRON) INFO (Running @reboot jobs)
Feb 22 12:32:22 boralus cron[623]: (CRON) INFO (Running @reboot jobs)
Feb 23 08:28:41 boralus cron[623]: (CRON) INFO (Running @reboot jobs)
Feb 23 12:21:12 boralus cron[623]: (CRON) INFO (Running @reboot jobs)
Feb 23 13:53:27 boralus cron[623]: (CRON) INFO (Running @reboot jobs)
Feb 23 17:44:38 boralus cron[623]: (CRON) INFO (Running @reboot jobs)
Feb 23 18:42:08 boralus cron[623]: (CRON) INFO (Running @reboot jobs)
Feb 23 21:18:52 boralus cron[623]: (CRON) INFO (Running @reboot jobs)
Feb 24 08:50:28 boralus cron[625]: (CRON) INFO (Running @reboot jobs)
Feb 24 10:05:41 boralus cron[625]: (CRON) INFO (Running @reboot jobs)
Feb 24 13:05:44 boralus cron[623]: (CRON) INFO (Running @reboot jobs)
Feb 24 15:36:57 boralus cron[625]: (CRON) INFO (Running @reboot jobs)
Feb 25 11:23:38 boralus cron[623]: (CRON) INFO (Running @reboot jobs)
Feb 25 14:46:33 boralus cron[623]: (CRON) INFO (Running @reboot jobs)
Feb 25 16:14:10 boralus cron[623]: (CRON) INFO (Running @reboot jobs)
Feb 25 17:45:42 boralus cron[623]: (CRON) INFO (Running @reboot jobs)
Feb 25 22:57:42 boralus cron[623]: (CRON) INFO (Running @reboot jobs)
Feb 26 06:06:24 boralus cron[623]: (CRON) INFO (Running @reboot jobs)
Feb 26 08:21:31 boralus cron[623]: (CRON) INFO (Running @reboot jobs)
Feb 26 22:27:33 boralus cron[623]: (CRON) INFO (Running @reboot jobs)
Feb 27 07:38:30 boralus cron[623]: (CRON) INFO (Running @reboot jobs)
Feb 27 19:37:31 boralus cron[623]: (CRON) INFO (Running @reboot jobs)
Feb 28 08:31:21 boralus cron[623]: (CRON) INFO (Running @reboot jobs)
Feb 28 22:42:52 boralus cron[623]: (CRON) INFO (Running @reboot jobs)
Mar  1 08:16:52 boralus cron[625]: (CRON) INFO (Running @reboot jobs)
Mar  1 08:27:16 boralus cron[623]: (CRON) INFO (Running @reboot jobs)
Mar  1 16:46:04 boralus cron[623]: (CRON) INFO (Running @reboot jobs)
Mar  1 16:50:07 boralus cron[625]: (CRON) INFO (Running @reboot jobs)
Mar  1 18:43:27 boralus cron[623]: (CRON) INFO (Running @reboot jobs)
Mar  1 20:10:38 boralus cron[623]: (CRON) INFO (Running @reboot jobs)
Mar  1 21:22:25 boralus cron[625]: (CRON) INFO (Running @reboot jobs)
Mar  1 22:45:54 boralus cron[625]: (CRON) INFO (Running @reboot jobs)
Mar  1 22:56:17 boralus cron[623]: (CRON) INFO (Running @reboot jobs)
Mar  2 00:07:23 boralus cron[623]: (CRON) INFO (Running @reboot jobs)
Mar  2 00:26:37 boralus cron[625]: (CRON) INFO (Running @reboot jobs)
Mar  2 07:08:01 boralus cron[625]: (CRON) INFO (Running @reboot jobs)
Mar  2 07:30:11 boralus cron[625]: (CRON) INFO (Running @reboot jobs)
Mar  2 11:13:41 boralus cron[625]: (CRON) INFO (Running @reboot jobs)
Mar  2 13:00:10 boralus cron[625]: (CRON) INFO (Running @reboot jobs)
Mar  2 13:16:03 boralus cron[623]: (CRON) INFO (Running @reboot jobs)
Mar  2 13:39:54 boralus cron[625]: (CRON) INFO (Running @reboot jobs)

This is UTC time.

Samuel

Reply via email to