#24 better "listen address" notation

Open
opened 5 years ago by boyska · 1 comments
boyska commented 5 years ago

for every listener, we currently have two options to separately handle unix domain sockets and tcp/udp addresses.

this is ugly, and doesn't scale well (see #13).

Goal of this issue is to have options that will understand more listener types.

for every listener, we currently have two options to separately handle unix domain sockets and tcp/udp addresses. this is ugly, and doesn't scale well (see #13). Goal of this issue is to have options that will understand more listener types.
boyska commented 5 years ago
Owner

Example:

1.2.3.4:8000 means port 8000, letting circolog decide protocol (udp/tcp) based on the context (ie: -syslogd-socket 1.2.3.4:8000 means UDP, while -query-socket localhost:8000 means TCP)

/asd/foo.sock means UNIX domain socket; whether datagram or stream is again decided by context (on -syslogd-socket it means datagram; on -query-socket it means stream)

@systemd means "assume that systemd socket activation is configured, and use that"

@inetd could mean (when it is implemented) "use inetd-style fd passing"

Example: `1.2.3.4:8000` means port 8000, letting circolog decide protocol (udp/tcp) based on the context (ie: `-syslogd-socket 1.2.3.4:8000` means UDP, while `-query-socket localhost:8000` means TCP) `/asd/foo.sock` means UNIX domain socket; whether datagram or stream is again decided by context (on `-syslogd-socket` it means datagram; on `-query-socket` it means stream) `@systemd` means "assume that systemd socket activation is configured, and use that" `@inetd` could mean (when it is implemented) "use inetd-style fd passing"
Sign in to join this conversation.
No Milestone
No assignee
1 Participants
Loading...
Cancel
Save
There is no content yet.