[Bug 215442] www/grafana3: directory /var/run/grafana3 not created at service start time (only at installation time)

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Tue Dec 20 14:55:24 UTC 2016


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215442

            Bug ID: 215442
           Summary: www/grafana3: directory /var/run/grafana3 not created
                    at service start time (only at installation time)
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs at FreeBSD.org
          Reporter: Mark.Martinec at ijs.si
                CC: jhixson at gmail.com
             Flags: maintainer-feedback?(jhixson at gmail.com)
                CC: jhixson at gmail.com

Please see Bug 213857 for details, discussion and a fix, the issue is
the same as it was for the databases/influxdb port, which is now fixed.

This same problem report also applies to www/grafana2 (do I need
to open a separate PR for that port?)


Using grafana3-3.1.1_1 on 11.0-RELEASE

A directory /var/run/grafana3 is assumed to exist at the grafana3 service
start time (to receive its pid file), yet the /usr/local/etc/rc.d/grafana3
startup script does not insure existence of this directory.
Instead, it relies on the package installation to create it.

This results in an grafana3 service failing to start if /var/run
is cleaned at machine boot time, or if it resides on an ephemeral
file system (like tmpfs), which is re-created at boot time.

Reliance on the installation script to create a directory on /var/run
is unlike most other ports, which populate the /var/run with whatever
they need during service startup time.

Please update the 'www/grafana3' port so that its
/usr/local/etc/rc.d/grafana3 script will create /var/run/grafana3
directory (if missing) at service startup time.

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


More information about the freebsd-ports-bugs mailing list