The seadrive logs on MacOS seem to grow for ever. So I tried to configure log rotation with MacOS newsyslog. However:
When using newsyslog to rotate SeaDrive logs on macOS, the client continues writing to the renamed file (e.g. seadrive.log.0) instead of the fresh seadrive.log. Even with copytruncate, SeaDrive sometimes reopens its log file and reattaches to the rotated copy, causing rotation to fail.
Unlike the Seafile server (which supports reopening logs with SIGUSR1), the SeaDrive client has no mechanism to reopen logs after rotation. This results in ever‑growing log files unless they are manually truncated or the File Provider process is restarted.
Suggestion:
Please add proper log handling to the SeaDrive client, for example by:
- Supporting a signal (e.g.
SIGUSR1) to reopen log files, or - Implementing built‑in log rotation (max size + rollover), or
- Using Apple’s native unified logging system (
os_log) which avoids manual log rotation altogether.
This would make SeaDrive easier to maintain on macOS systems and prevent runaway log file growth.
Thank you!