[Bug 203951] syncthing-inotify
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Thu Oct 22 11:42:02 UTC 2015
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203951
Bug ID: 203951
Summary: syncthing-inotify
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Many People
Priority: ---
Component: Individual Port(s)
Assignee: freebsd-ports-bugs at FreeBSD.org
Reporter: bannereddivpool at gmail.com
Syncthing-inotify needs a service. Unfortunately after testing some scenarios
the system would hang with large file limits causing an extreme delay on
startup. Utilizing screen seems to take care of the issue
Further testing on a very decent hardware cluster sysctl kern.maxfiles does get
limited as syncthing-inotify needs to open files to watch for changes. sysctl
-a |grep kern.maxfiles will certainly show you when this has been reached. I
listed other affected sysctl functions below that will need to be checked.
Below is my service "watch" if we can add to syncthing-inotify.
#!/bin/sh
#
# PROVIDE: syncthing
# REQUIRE: LOGIN
# KEYWORD: shutdown
#
# Add the following lines to /etc/rc.conf.local or /etc/rc.conf
# to enable this service:
# watch_enable="YES"
#
# This program requires screen to run
#
# Please Change the -target="" to the address that syncthing is running. By
Default this is 127.0.0.1:8384 -target="http://127.0.0.1:8384"
# The API key will need to reflect that of what is generated by syncthing
#
# Adjust the following to match the desired file capacity in /etc/sysctl.conf;
#
# kern.maxfiles="2000000"
# kern.maxfilesperproc="2000000"
# kern.maxvnodes="900000"
#
# Larger file systems over will need these to run.
#
. /etc/rc.subr
name=watch
rcvar=watch_enable
load_rc_config $name
: ${watch_enable:="NO"}
: ${watch_user:="root"}
: ${watch_group:="wheel"}
command="/usr/local/bin/screen"
command_args="-d -m /usr/local/bin/syncthing-inotify
-target="http://127.0.0.1:8384" -verbosity="4" -api="KEY HERE""
run_rc_command "$1"
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list