Bring back changing Syslog location away from boot pool

I miss having syslog keeping my hdds spinning and remove needless wear on my cheap boot ssds. Any chance for bringing back syslog location settings? I think the previous official justification was to make it more optimized for bug reports, but I’m not imaginative enough to understand how a fixed location impacts this.

Problem/Justification
Reduce needless writes on boot SSDs by more logs to other pools. SSDs are recommended for boot pool, no point in writing needlessly to them imo.

Impact
Arguably improves longevity to SSD boot pools by reducing amount of writes.

User Story
Re-introduce the old UI options of being able to set the boot pool location. To my ignorant mind that knows nothing of the background of why this was changed, seems like a simple feature reintroduction with minimal consequence/effort.

1 Like

Everything you said plus this would also allow us to store the syslog on an encrypted System Dataset, which we currently can do with Core.

2 Likes

Reasoning was posted in old forums.

I would argue that if the syslog is so important, the ability to place it in a more resilient pool than the boot pool should be a given.

:smirk:

1 Like