Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 10 Feb 2023 23:45:21 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 269480] sysutils/fluent-bit: rc.d script should not use --daemon option when combined with daemon command
Message-ID:  <bug-269480-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D269480

            Bug ID: 269480
           Summary: sysutils/fluent-bit: rc.d script should not use
                    --daemon option when combined with daemon command
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: girgen@FreeBSD.org
          Reporter: hiroo.ono+freebsd@gmail.com
             Flags: maintainer-feedback?(girgen@FreeBSD.org)
          Assignee: girgen@FreeBSD.org

Created attachment 240071
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D240071&action=
=3Dedit
patch to fluent-bit.in

The option --daemon is passed to fluent-bit in the rc.d script. This makes =
the
pid of fluent-bit not matching with the one written if /var/run/fluent-bit.=
pid.
The file /var/run/fluent-bit.pid is written by daemon command, where the va=
lue
is the pid of the child process which executes fluent-bit. If you pass --da=
emon
option, fluent-bit itself forks and executes again and the pid becomes
different  from the pid written in the pid file.
Try 'service fluent-bit start' and see the value of 'pgrep fluent-bit' and =
'cat
/var/run/fluent-bit.pid'.
This makes 'service fluent-bit stop' and 'service fluent-bit status' not
working. Also, the daemon command daemonize a program running foreground, so
there is no need to set --daemon option to fluent-bit.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-269480-7788>