@pst said in Syslogs starts late in the boot process leading to misrepresentation of events (incorrect time stamps):
Apr 19 22:29:33 syslogd kernel boot file is /boot/kernel/kernel
Apr 19 22:25:04 syslogd exiting on signal 15
Yep, over 4 minutes. A bit long indeed.
But like any other OS there : how would it be able to "log" ?
Its the chicken and egg problem. How can something get written to a disk, if the device doesn't even know it has a 'disk' to write to ? Better : when a system boot, some BIOS code starts, and it doesn't even know that it is going to boot Windows, or Debian, or pfSense .... or your coffee machine.
So, no, about disk, file system, file acls etc ...
Only when the system detected that it had a 'drive', and this drive has a bootable partition, and this bootable partition is loaded, and the OS kick started, and the OS (kernel) start to make an inventory of the entire system, and it will detect 'user drives', starts up multi processing, kicks of the first process, then launches all system processes, like "syslogd", which only then, at that moment, can start collecting 'logs' and write them to a disk.
But ... don't worry, there are solutions.
The first one : for devices with a graphics card : hook up that screen, and power up the system. You will "see" boot info.
If there is no graphics adapter, then use the serial "RS232" access. This is even better as now you can log, if needed, what the boot process produced.
The kernel itself, before it can actually 'log to a disk' will keep the log into its own memory before writing it out way latter : see here : Status > System Logs > System > OS Boot
@pst said in Syslogs starts late in the boot process leading to misrepresentation of events (incorrect time stamps):
24/04/2024 11:09:19 L248: system_do_shell_commands(1);
Normally, there are none.
If there are any, ask the admin, as he put them there.
This package exists :
7a11c877-b6ad-4772-834f-560fdf4f8d61-image.png
and go here : Services>Shellcmd Settings
so you can see them (before, we were editing the config.xml ourselves)
Btw : in my config.xml :
4cc96c07-21f1-4fb1-b10f-67dd847ac24d-image.png
so the patches packages also installs 'hook' so it can patch the system as soon as possible, if needed.
Right now, on my 24.03 Release, the patches package is pretty empty.