Skip to content
New issue

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

Consultation on issues with version 0.5.0 #81

Open
meguoe opened this issue Sep 26, 2024 · 0 comments
Open

Consultation on issues with version 0.5.0 #81

meguoe opened this issue Sep 26, 2024 · 0 comments

Comments

@meguoe
Copy link

meguoe commented Sep 26, 2024

This is the content of my configuration file.

system {
    threads-per-service 24
    daemonize true
    pid-file "/tmp/river.pid"
    upgrade-socket "/tmp/river.sock"
}
services {
    Server {
        listeners {
            "0.0.0.0:80"
        }
        connectors {
            "192.168.110.110:7003"
        }
    }
}

1、Is it normal that repeating the startup command three times creates three processes without any conflicts?
river --config-kdl config.kdl --pidfile="/tmp/river.pid" --upgrade-socket="/tmp/river.sock" --threads-per-service=24 --daemonize
image

2、Not creating the upgrade-socket file.
image

3、An error is prompted when specifying --upgrade for hot loading.
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant