| Main index | Section 8 | Options |
The hostapd utility is designed to be a "daemon" program that runs in the background and acts as the backend component controlling the wireless connection. It supports separate frontend programs such as the text-based frontend, hostapd_cli(8).
The following arguments must be specified on the command line:
| config-file | |
|
Use the settings in the specified configuration file; the name of
the specified wireless interface is contained in this file.
See
hostapd.conf(5)
for a description of the configuration file syntax.
Changes to the configuration file can be reloaded by sending a SIGHUP to the hostapd processor or with the hostapd_cli(8) utility, using "hostapd_cli reconfigure". | |
| | |
| Enable debugging messages. If this option is supplied twice, more verbose messages are displayed. | |
| | |
| Show help text. | |
| | |
| Include timestamps in debugging output. | |
| | |
| Display version information on the terminal and exit. | |
| | |
| Detach from the controlling terminal and run as a daemon process in the background. | |
| | |
| Include key information in debugging output. | |
| | |
| Store PID in pidfile. | |
| HOSTAPD (8) | July 18, 2012 |
| Main index | Section 8 | Options |
Please direct any comments about this manual page service to Ben Bullock. Privacy policy.
| “ | Never write it in C if you can do it in `awk'; Never do it in `awk' if `sed' can handle it; Never use `sed' when `tr' can do the job; Never invoke `tr' when `cat' is sufficient; Avoid using `cat' whenever possible. |
” |
| — Taylor's Laws of Programming | ||