Save log file on USR1 signal

[qwerty287]

This is an exciting feature.

If you send a USR1 signal to woodpecker, will it "release" the file so the host can logrotate it?

Originally posted by @lonix1 in #2115 (comment)

If you send a USR1 signal to woodpecker, will it "release" the file so the host can logrotate it?

not jet that's a followup ... I need to write a wrapper for the os.FileOpen that can do so ... so that's a followup

Originally posted by @6543 in #2115 (comment)

I just created this mentioned wrapper as lib here: https://github.com/6543/logfile-open ...
... so once merged I can create a followup, that can be tested seperate

Originally posted by @6543 in #2115 (comment)

[lonix1]

It's not really about saving the file on receiving the signal - actually the idea when receiving the SIGUSR1 signal, is to release (/close) and recreate the log file.

Once the host does something with that file (e.g. logrotate it) the woodpecker process must let go of the file handle (i.e. close file), else it will continue writing to the same file. So it should close the file then reopen it with the same name.

[6543]

-> #2151