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
I'm configuring renderd on a separate machine than the one wit Apache/mod_tile, so I'm obliged to put this in renderd.conf:
renderd
mod_tile
renderd.conf
iphostname=0.0.0.0 ipport=7654
But if I also want to test that it's running properly with render_list, I need the Unix socket, because I can't tell it the IP/port to connect to, so:
render_list
socketname=/var/run/renderd/renderd.sock
renderd ignores the latter:
Sep 16 11:47:16 diablo renderd[4832]: Parsing section renderd Sep 16 11:47:16 diablo renderd[4832]: config renderd: ip socket=0.0.0.0:7654 Sep 16 11:47:16 diablo renderd[4832]: config renderd: num_threads=2tile Sep 16 11:47:16 diablo renderd[4832]: config renderd: num_slaves=0 Sep 16 11:47:16 diablo renderd[4832]: config renderd: tile_dir=/var/lib/mod_tile Sep 16 11:47:16 diablo renderd[4832]: config renderd: stats_file=/var/run/renderd/renderd.stats
Maybe the easiest way to solve this is to teach render_* to use a TCP/IP address.
render_*
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
I'm configuring
renderd
on a separate machine than the one wit Apache/mod_tile
, so I'm obliged to put this inrenderd.conf
:But if I also want to test that it's running properly with
render_list
, I need the Unix socket, because I can't tell it the IP/port to connect to, so:renderd
ignores the latter:Maybe the easiest way to solve this is to teach
render_*
to use a TCP/IP address.The text was updated successfully, but these errors were encountered: