FreeBSD port #661

New issue

Closed

opened 2023-10-22 18:54:09 +00:00 by vk · 2 comments

vk commented

2023-10-22 18:54:09 +00:00

Contributor

Hello,

I wanted to try out garage on FreeBSD, by setting up a 3 nodes cluster.

While a FreeBSD port does exist, it doesn't seem quite up to date (it's still providing 0.8.4), and the rc.d (FreeBSD equivalent to old Linux' init.d) script seems broken - service garage launches in foreground while writing to stdout, preventing it from starting on server/jail/VM boot.

So, my actual questions:

is the FreeBSD port official (ie. provided by you, the authors)?
Is there a command-line option to garage server (the help doesn't mention any) to actually make it detach from foreground, and write the output elsewhere than stdout? I know I could get around this by other means, but I like to stick to built-in behavior, and official ports/packages.

Thanks
Kind regards

Hello, I wanted to try out garage on FreeBSD, by setting up a 3 nodes cluster. While a FreeBSD port does exist, it doesn't seem quite up to date (it's still providing 0.8.4), and the rc.d (FreeBSD equivalent to old Linux' init.d) script seems broken - `service garage` launches in foreground while writing to stdout, preventing it from starting on server/jail/VM boot. So, my actual questions: 1) is the FreeBSD port official (ie. provided by you, the authors)? 2) Is there a command-line option to `garage server` (the help doesn't mention any) to actually make it detach from foreground, and write the output elsewhere than stdout? I know I could get around this by other means, but I like to stick to built-in behavior, and official ports/packages. Thanks Kind regards

lx commented

2023-10-23 10:18:47 +00:00

Owner

Hi, thanks for your interest in Garage.

No, we are not responsible for the FreeBSD port. Please find the FreeBSD maintainer and communicate any issues with them. The release of 0.8.4 is quite recent so I'm certain they are still actively maintaining it.
There is not. We are generally trying to stick to a philosophy of not embedding in Garage any behaviour that can be easily achieved by composition with external programs (something like the "unix philosophy").

Hi, thanks for your interest in Garage. 1. No, we are not responsible for the FreeBSD port. Please find the FreeBSD maintainer and communicate any issues with them. The release of 0.8.4 is quite recent so I'm certain they are still actively maintaining it. 2. There is not. We are generally trying to stick to a philosophy of not embedding in Garage any behaviour that can be easily achieved by composition with external programs (something like the "unix philosophy").

lx closed this issue

2023-10-23 10:18:47 +00:00

vk commented

2023-10-30 11:02:02 +00:00

Author

Contributor

Hi,

Thanks for the feedback.

I have submitted a bug report to the FreeBSD port maintainer.

Regarding stdout/stderr and logging: while I do understand your stance, I would also argue that most unix daemons provide alternative ways of logging (syslog or log files), that, unlike the stderr stategy, support logs management (ie. rotation).

I've noticed that issue #368 mentions a syslog patch, which unfortunately wasn't merged due to author not submitting a PR (possibly because he's unaware of your reply - this git install doesn't seem to send emails on issue replies - I haven't received any).

Hi, Thanks for the feedback. I have submitted a bug report to the FreeBSD port maintainer. Regarding stdout/stderr and logging: while I do understand your stance, I would also argue that most unix daemons provide alternative ways of logging (syslog or log files), that, unlike the stderr stategy, support logs management (ie. rotation). I've noticed that issue #368 mentions a syslog patch, which unfortunately wasn't merged due to author not submitting a PR (possibly because he's unaware of your reply - this git install doesn't seem to send emails on issue replies - I haven't received any).

No milestone

No project

No assignees

2 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Deuxfleurs/garage#661

No description provided.