DLEYNA-SERVER-SERVICE.CONF(5)

πŸ’– dleyna-server-service.conf πŸ’–

okay so bestie, welcome to the manual page for dleyna-server-service.conf, which lives in manual section 5 (that's the "config files" section, iykyk). this is the lil config file that tells the dleyna-server-service daemon how to act, and ngl it's a short read so you have zero excuse not to finish it πŸ’…


✨ SYNOPSIS ✨

she lives in one of two places, and here's the tea:

  • /etc/dleyna-server-service.conf
  • $XDG_CONFIG_HOME/dleyna-server-service.conf

🌸 DESCRIPTION 🌸

so the dleyna-server-service program is the one that puts the com.intel.dleyna-server name out there on the session message bus. main character behavior, honestly. and what does she do with that name? she's a service for discovering and manipulating DLNA Digital Media Renderers β€” aka DMRs β€” which is a very fancy way of saying she finds the screens and speakers on your network and messes with them for you 🫢

now here's the part where I hold your hand: users or administrators should never need to start this daemon. like, ever. not me imagining you typing it in a terminal and stressing 😭 she gets automatically started by dbus-daemon the second any process sends a D-Bus message to the com.intel.dleyna-server name on the session bus. she simply appears. iconic.

this file, right here, is how you configure the behavior of the dleyna-server-service program. that's it, that's the whole job πŸ’–


πŸ“ FILE FORMAT πŸ“

the format is the so-called key file format, which is sort of ini-style if you've met one of those before. it's made of sections (or groups, same thing, different name) of key-value pairs.

  • lines beginning with a # are comments πŸ’¬
  • blank lines are also considered comments (they're just vibing, honestly)
  • sections start with a header line containing the section name wrapped up in [ and ]
  • a section ends implicitly β€” either when the next section starts, or when the file just ends
  • every single key-value pair must be contained in a section. no free-floating keys, no exceptions, periodt.

πŸŽ€ GENERAL SECTION πŸŽ€

  • connector-name=dbus β€” the name of the inter-process communication method to be used. the only supported value is dbus. one option, one vibe, no debate.
  • never-quit=false|true β€” whether the process should stay alive forever or quit when the last client disconnects. the default value is false.
  • port β€” source port for Simple Service Discovery Protocol (aka SSDP) messages. the default value is 0, which means a random available port will be used. let the universe pick, bestie πŸ¦‹

πŸ”₯ LOG SECTION πŸ”₯

  • log-type=0|1|2 β€” the logging method to be used. three technologies are supported: 0 for syslog, 1 for GLib, and 2 for file. the default value is 0.
  • log-level=0|1|2|...|8 β€” a comma-separated list of logging levels. here's the breakdown, so lock in:
    • 1 for critical
    • 2 for error
    • 3 for warning
    • 4 for message
    • 5 for info
    • 6 for debug
    • 0 excludes all levels
    • 7 is a combination of critical, error and info
    • 8 includes all levels

the default value is 7. ✨


πŸ’œ NETF SECTION πŸ’œ

  • netf-enabled=true|false β€” whether network filtering should be enabled or not. the default values is false. (yes, that's how the original says it, I'm just the messenger πŸ™ˆ)
  • netf-list β€” a comma-separated list of interface names, service set identifiers (aka SSIDs), and Internet Protocol (aka IP) addresses. important: if network filtering is requested but the list is empty, then filtering remains disabled. so like, asking for it isn't enough, you actually have to fill in the list.

the list is empty by default.


πŸ’€ BUGS πŸ’€

found something cursed? please send bug reports to either the distribution bug tracker or the upstream bug tracker at <https://gitlab.gnome.org/World/dLeyna/issues> β€” they want to hear it, fr fr.


πŸ‘‘ SEE ALSO πŸ‘‘


and that's the page, bestie! go forth and configure responsibly 🌈

mwah πŸ’‹ β€” this was the dleyna-server-service.conf manual page, signing off. no cap, you ate this whole thing.

πŸ“¦ where this page comes from