NASD(1)
π NAME π
okay so <pink>nasd</pink> is the Network Audio System server β that's the whole vibe bestie, it's the generic name for the Network Audio System server. And lowkey the tea is that it's frequently a link or a copy of the appropriate server binary for driving the most frequently used server on a given machine. slay. π
This page lives in the General Commands Manual, and the command itself is just <pink>nasd</pink>. π
β¨ SYNOPSIS β¨
nasd [:listen port offset] [-option ...]
π¦ DESCRIPTION π¦
nasd is the generic name for the Network Audio System server. It is frequently a link or a copy of the appropriate server binary for driving the most frequently used server on a given machine. periodt. π
πΈ STARTING THE SERVER πΈ
The server is usually started from /etc/rc or a user's startup script. very demure, very startup-script of it.
When the Network Audio System server starts up, it takes over /dev/audio. π§ Not me just grabbing the audio device like it's mine.
Note, that ifReleaseDeviceis set toTRUE[default] in thenasd.conffile,nasdwill relinquish control of the audio device whenever it has finished playing a sound. This means you can use other non-NAS applications whennasdis running, as long asnasdisn't currently playing a song. π΅
If ReleaseDevice is set to FALSE in the nasd.conf file, applications that attempt to access /dev/audio themselves will fail while nasd is running. π so possessive of it fr fr.
π NETWORK CONNECTIONS π
The Network Audio System server supports connections made using the following reliable byte-streams:
- TCPIP β The server listens on port
8000+n, wherenis the listen port offset. - Unix Domain β The X server uses
/tmp/.sockets/audionas the filename for the socket, wherenis the display number.
π OPTIONS π
All of the Network Audio System servers accept the following generic command line options. Options specific to a particular server may also be available, and are not listed here. Try nasd -? for a list of those options, if available. iykyk π«Ά
-aaβ Allows any client to connect. By default, access is allowed only to authenticated clients. (no bouncer at the door, everyone's invited π)-localβ Allows only clients on the local host to connect. By default, access is allowed to local and remote hosts.-vβ Enable verbose messages. This option overrides thenasd.conffile setting. she's chatty π¬-Vβ Print version information and exit (ignoring other options).-bβ Fork a child to run in the background and exit (daemon mode). Messages are sent tosysloginstead ofstderr.-d nβ Enable debugging output at level n, where n is a positive integer. The higher the level, the more output you will get. A value of0[default] disables debugging output. This option overrides thenasd.conffile setting. the way that n just keeps going up π₯-pn-nopn[default] β Enables or disables Partial Networking. Enabling Partial Networking allows the server to start, even if the server cannot establish all of its well-known sockets (connection points for clients), but establishes at least one. it's giving "we tried our best and that's enough" π-config fileβ Use the config file file, instead of the default (/etc/nasd/nasd.conf).
π SIGNALS π
The Network Audio System server attaches special meaning to the following signals:
SIGHUPβ This signal causes the server to close all existing connections, free all resources, and restore all defaults. full factory reset energy β¨SIGTERMβ This signal causes the server to exit cleanly. leaving the party politely πͺSIGUSR1β This signal is used quite differently from either of the above. When the server starts, it checks to see if it has inheritedSIGUSR1asSIG_IGNinstead of the usualSIG_DFL. In this case, the server sends aSIGUSR1to its parent process after it has set up the various connection schemes. it's giving "text me when you're home safe" π
π DIAGNOSTICS π
Too numerous to list them all. bestie there are so many we simply cannot π«
π FILES π
/tmp/.sockets/audio*β Unix domain socket/usr/adm/audio*msgs/dev/audioβ Audio device
β SEE ALSO β
nas(1), auinfo(1), auplay(1), auctl(1), nasd.conf(1)
π BUGS π
If au dies before its clients, new clients won't be able to connect until all existing connections have their TCP TIME_WAIT timers expire. not the TIME_WAIT timer era π
The current access control support is weak at best. ngl. it's giving wet paper towel π§»
π COPYRIGHT π
Copyright 1993, Network Computing Devices, Inc.
π AUTHORS π
The Network Audio System server was originally written by Greg Renda and Dave Lemke, with large amounts of code borrowed from the sample X server.
The sample X server was originally written by Susan Angebranndt, Raymond Drewry, Philip Karlton, and Todd Newman, from Digital Equipment Corporation, with support from a large cast. It has since been extensively rewritten by Keith Packard and Bob Scheifler, from MIT. legends only, no cap π
and that's the whole page bestie!! π¦ this was the NASD(1) page from the General Commands Manual β that's the source and the page number right there at the bottom, sitting pretty. mwah, go play some sounds πβ¨π
π¦ where this page comes from
- fedora 43: nas 1.9.5-11.fc41 Β· MIT
- fedora 43: nas 1.9.5-14.fc43 Β· MIT
- fedora 44: nas 1.9.5-15.fc44 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms