We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't run daemonded, daemon-tty, etc. on some Linux, here with daemonded:
daemonded
daemon-tty
Warn: Could not bind singleton socket at file: "/tmp/.unvanquished-server-3893AD6762EA7A4328C37822C2B8727E/socket", error: "No such file or directory"
It is related to the filesytem, if I use TMPDIR="$(pwd)" (and then use another filesystem than /tmp) it works.
TMPDIR="$(pwd)"
/tmp
The text was updated successfully, but these errors were encountered:
/
ext4 defaults,relatime,lazytime,errors=remount-ro
Sorry, something went wrong.
With daemon-tty:
Warn: Could not bind singleton socket at file: "/tmp/.unvanquished-3893AD6762EA7A4328C37822C2B8727E/socket", error: "No such file or directory"
Forget about it, logs were full and because /tmp was not a separate partition, it could not write to it.
Because I first experienced the macOS bug I then believed it was a variant of it:
No branches or pull requests
Can't run
daemonded
,daemon-tty
, etc. on some Linux, here withdaemonded
:It is related to the filesytem, if I use
TMPDIR="$(pwd)"
(and then use another filesystem than/tmp
) it works.The text was updated successfully, but these errors were encountered: