Tree: f946040fa9

develop

docker/socat

drone-ci

master

v0.10

v0.10.1

v0.10.18

v0.10.8

v0.10rc

v0.11

v0.11.19

v0.11.29

v0.11.33

v0.11.34

v0.11.4

v0.11.43

v0.11.53

v0.11.66

v0.11rc

v0.2.0

v0.3.0

v0.3.1

v0.4.0

v0.4.1

v0.4.2

v0.5.0

v0.5.11

v0.5.13

v0.5.2

v0.5.5

v0.5.8

v0.5.9

v0.6.0

v0.6.1

v0.6.15

v0.6.3

v0.6.5

v0.6.9

v0.7.0

v0.7.19

v0.7.22

v0.7.33

v0.7.6

v0.8.0

v0.8.10

v0.8.25

v0.8.43

v0.9.0

v0.9.113

v0.9.128

v0.9.13

v0.9.141

v0.9.46

v0.9.48

v0.9.60

v0.9.71

v0.9.97

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'f946040fa9'

${ noResults }

Commit Graph

4 Commits (f946040fa94a3acb3b1f54873e6f95766595829c)

Author	SHA1	Message	Date
Koen Wilde	4db0e1d340	Fix status command in FreeBSD init script ... If the init script is called with `status`, the rc.subr(8) routines check if the first argument associated with the pid in the pidfile is equal to `procname`. By default, `procname` is equal to the value of `command`. In our case, `command` contains a space (i.e. has multiple arguments), so `procname` can never be equal to the first argument of the command associated with the pid. Set `procname` to the first argument of `command` to fix the `status` command of the init script.	9 years ago
Renato Aquino	923c45d721	HOME fix into FreeBSD init script	9 years ago
William Friesen	bfef8f0edd	Fix command used by FreeBSD init script	10 years ago
Clint Armstrong	66a9c0d71d	Rename scripts/rc/freebsd/gogs to scripts/init/freebsd/gogs	10 years ago