package/owfs: delay sysvinit start until after network and avahi
PATCH 1/1 package/owfs: delay sysvinit start until after network and avahi
In its default configuration, owserver opens a TCP socket on the 'lo' interface. However, in some situations, the 'lo' interface may not yet be up until S40network is started. This causes owserver not to start its TCP socket, which makes it impossible for the owfs client to connect to it.
In addition, owserver may have avahi integration.
Therefore, delay the start of owserver and owfs until after S40network and S50avahi-daemon.
---
package/owfs/{S25owserver => S55owserver} | 0
package/owfs/{S30owfs => S60owfs} | 0
package/owfs/owfs.mk | 8 ++++----
3 files changed, 4 insertions(+), 4 deletions(-)
rename package/owfs/{S25owserver => S55owserver} (100%)
rename package/owfs/{S30owfs => S60owfs} (100%)package/owfs/S55owserver renamed from package/owfs/S25owserver +0 -0
package/owfs/S60owfs renamed from package/owfs/S30owfs +0 -0
package/owfs/owfs.mk +4 -4
@@ -31,8 +31,8 @@ OWFS_CONF_OPTS += \ --with-fuseinclude=$(STAGING_DIR)/usr/include \ --with-fuselib=$(STAGING_DIR)/usr/lib define OWFS_INSTALL_FUSE_INIT_SYSV - $(INSTALL) -D -m 0755 $(OWFS_PKGDIR)S30owfs \ - $(TARGET_DIR)/etc/init.d/S30owfs + $(INSTALL) -D -m 0755 $(OWFS_PKGDIR)S60owfs \ + $(TARGET_DIR)/etc/init.d/S60owfs endef define OWFS_CREATE_MOUNTPOINT mkdir -p $(TARGET_DIR)/dev/1wire
@@ -102,8 +102,8 @@ endif OWFS_MAKE = $(MAKE) $(OWFS_EXTRA_MAKE_OPTS) define OWFS_INSTALL_INIT_SYSV - $(INSTALL) -D -m 0755 $(OWFS_PKGDIR)S25owserver \ - $(TARGET_DIR)/etc/init.d/S25owserver + $(INSTALL) -D -m 0755 $(OWFS_PKGDIR)S55owserver \ + $(TARGET_DIR)/etc/init.d/S55owserver $(OWFS_INSTALL_FUSE_INIT_SYSV) endef
Signature · 1 line
2.20.1
PATCH 1/1 package/owfs: delay sysvinit start until after network and avahi
Quoted 8 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Arnout" == Arnout Vandecappelle (Essensium/Mind) <[email protected]> writes:
In its default configuration, owserver opens a TCP socket on the 'lo' interface. However, in some situations, the 'lo' interface may not yet be up until S40network is started. This causes owserver not to start its TCP socket, which makes it impossible for the owfs client to connect to it.
Quoted 6 lines
In addition, owserver may have avahi integration.
Therefore, delay the start of owserver and owfs until after S40network and S50avahi-daemon.
Committed, thanks.
Signature · 1 line
Bye, Peter Korsgaard
PATCH 1/1 package/owfs: delay sysvinit start until after network and avahi
In reply to Arnout Vandecappelle (Essensium/Mind)Quoted 8 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Arnout" == Arnout Vandecappelle (Essensium/Mind) <[email protected]> writes:
In its default configuration, owserver opens a TCP socket on the 'lo' interface. However, in some situations, the 'lo' interface may not yet be up until S40network is started. This causes owserver not to start its TCP socket, which makes it impossible for the owfs client to connect to it.
Quoted 6 lines
In addition, owserver may have avahi integration.
Therefore, delay the start of owserver and owfs until after S40network and S50avahi-daemon.
Committed to 2019.02.x, thanks.
Signature · 1 line
Bye, Peter Korsgaard