44%
20.06.2022
. It can be configured by editing two files: /etc/dnsmasq.conf and /etc/hosts. (See also the "Integrating the Domain Controller" box.) The /etc/hosts file has the names of the local systems for the DNS
44%
30.04.2013
it to match. For a simple example, configuring an Apache site might require the existence of the following file:
/etc/apache2/sites-enabled/my-site.conf
Or, you might want to make sure a module is configured
44%
22.12.2017
://localhost/documents
This time, Subversion is working in both worlds.
Be aware that to write data, you need to add the anon-access = write line to the conf/svnserve.conf file in the root directory of the C
44%
05.02.2019
SuiteCRM application:
sudo cd /etc/apache2/sites-available
sudo touch suitecrm.conf
sudo nano -w suitecrm.com
Now copy the code shown in Listing 1 [4] into the nano text editor window to populate
44%
20.05.2014
to be monitored is launched by zabbix_agentd. Until the web interface is installed, you need to set up the agent manually in the respective /usr/local/etc/zabbix_agentd.conf configuration file on the host you want
44%
11.10.2016
is simple to configure, needing only the http2 inline directive; this ensures that Nginx can also open TLS port 443, such as in the /etc/nginx/conf.d/default.conf file:
listen 443 ssl http2;
HTTP/2
44%
18.07.2013
. For example, configuring an Apache site might require the existence of the file /etc/apache2/sites-enabled/.conf, or you might want to make sure a module is configured as you desire: /etc/apache2/conf.d/.conf
44%
03.02.2022
Linc configuration file opt/thinlinc/etc/conf.d. To do so, generate a new profile by editing the profiles.hconf file, which could look as follows in an instance where Firefox is the only permitted application
44%
07.04.2022
in the inventory. If clients do not have direct access to the Internet, you can enter an HTTP proxy in the rport.conf client configuration file. An example is included in the file.
Tunnel Instead of VPN
The wish
44%
22.10.2012
(device0
, device2
, … and host1
, host2
, …) must be adapted to the local conditions. Thus, the name of the device should correspond to the device name in ceph.conf
(in this example: osd.0
