You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 30, 2018. It is now read-only.
Replace the values below using the output from storjshare --version.
* daemon: 2.1.2, core: 6.0.15, protocol: 1.1.0
Replace the values below using the output from node --version.
6.9.2
Expected Behavior
Desire the ability to query via the storjshare command if the daemon is running. DO NOT want it to autostart if its down, since the query may be running on a different userid than the shares are normally spawned on.
Output can be minimal, but please set different return codes for up and down so the status can be checked in script.
Perhaps a "--status" option on the "storjshare daemon" command?
Alternative: have the daemon issue an "autosave" on some configurable timeframe (e.g. "storjshare daemon autosave 600" for a 10 minute event) and autoload upon failure. This, of course, would imply a high level catch be added to capture any future potential outage.
Another alternative: have the daemon create a pid file that an external script could check.
Actual Behavior
The daemon process looks very similar to share processes, with everything being identified by the OS as command "node". Counting "node" processes to see if the daemon is running is crude and relatively expensive on machines with 10's of thousands of processes running.
Steps to Reproduce
Please include the steps the reproduce the issue, numbered below. Include as
much detail as possible.
...
...
...
The text was updated successfully, but these errors were encountered:
Package Versions
Replace the values below using the output from
storjshare --version
.Replace the values below using the output from
node --version
.Expected Behavior
Desire the ability to query via the storjshare command if the daemon is running. DO NOT want it to autostart if its down, since the query may be running on a different userid than the shares are normally spawned on.
Output can be minimal, but please set different return codes for up and down so the status can be checked in script.
Perhaps a "--status" option on the "storjshare daemon" command?
Alternative: have the daemon issue an "autosave" on some configurable timeframe (e.g. "storjshare daemon autosave 600" for a 10 minute event) and autoload upon failure. This, of course, would imply a high level catch be added to capture any future potential outage.
Another alternative: have the daemon create a pid file that an external script could check.
Actual Behavior
The daemon process looks very similar to share processes, with everything being identified by the OS as command "node". Counting "node" processes to see if the daemon is running is crude and relatively expensive on machines with 10's of thousands of processes running.
Steps to Reproduce
Please include the steps the reproduce the issue, numbered below. Include as
much detail as possible.
The text was updated successfully, but these errors were encountered: