I was trying to install Pi-hole on docker using youtube tutorials , the first thing they did was to stop and disable systemd-resolved.service but even after doing that dns service was not permanently disabled.
> [utkarsh@Asus ~]$ sudo systemctl stop systemd-resolved.service
> [sudo] password for utkarsh:
> [utkarsh@Asus ~]$ sudo systemctl disable systemd-resolved.service
> [utkarsh@Asus ~]$ sudo systemctl status systemd-resolved.service
> ● systemd-resolved.service - Network Name Resolution
> Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; disabled; vendor preset: enabled)
> Active: inactive (dead)
> Docs: man:systemd-resolved.service(8)
> man:org.freedesktop.resolve1(5)
> https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
> https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
>
> May 19 18:47:21 Asus systemd-resolved[700]: Positive Trust Anchors:
> May 19 18:47:21 Asus systemd-resolved[700]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
> May 19 18:47:21 Asus systemd-resolved[700]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21>
> May 19 18:47:21 Asus systemd-resolved[700]: Using system hostname 'Asus'.
> May 19 18:47:21 Asus systemd[1]: Started Network Name Resolution.
> May 19 18:48:16 Asus systemd-resolved[700]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 192.168.43.1.
> May 19 18:51:12 Asus systemd-resolved[700]: Failed to emit notification about changed property CurrentDNSServer: Transport endpoint is not connected
> May 19 18:51:12 Asus systemd[1]: Stopping Network Name Resolution...
> May 19 18:51:12 Asus systemd[1]: systemd-resolved.service: Succeeded.
> May 19 18:51:12 Asus systemd[1]: Stopped Network Name Resolution.
>
> [utkarsh@Asus ~]$ ping google.com
> PING google.com(del12s01-in-x0e.1e100.net (2404:6800:4002:81e::200e)) 56 data bytes
> 64 bytes from del12s01-in-x0e.1e100.net (2404:6800:4002:81e::200e): icmp_seq=1 ttl=117 time=55.6 ms
> 64 bytes from del12s01-in-x0e.1e100.net (2404:6800:4002:81e::200e): icmp_seq=2 ttl=117 time=59.7 ms
> 64 bytes from del12s01-in-x0e.1e100.net (2404:6800:4002:81e::200e): icmp_seq=3 ttl=117 time=62.9 ms
> 64 bytes from del12s01-in-x0e.1e100.net (2404:6800:4002:81e::200e): icmp_seq=4 ttl=117 time=122 ms
This question is completely unrelated to Manjaro.
Manjaro does not use systemd-networkd or systemd-resolved but Network Manager.
So, how can i disable it ?
(Sorry, i am a complete noob).
The fact that you follow a guide without even knowing how your system works.
Trying to disable a service which is not running on a default Manjaro system - then you have to ask how disable a core system component - it leaves me the impression you lack basic knowledge to accomplish the goal .
But we learn by doing - so dive in - recommended reading Pi-hole - ArchWiki.
systemctl is the key to the services on the system.
- A service can be stopped - which is temporary - it will activate after a system restart.
- A service can be disabled - which is permanent - it will not activate after system restart
- A service can be started - which is temporary - it will not activate after system restart
- A service can be enabled - which is permanent - it will activate after system restart
- A service can be enabled/disabled and started/stopped in one command by adding the keyword --now
So to stop and disable NetworkManager
sudo systemctl disable --now NetworkManager
Have fun and please read the forum rules found at Forum Rules - Manjaro perhaps starting with this Life is a Two-way Street
Thank you for replying , initially i was trying to use the ArchWiki manual for Pi-Hole setup but i got stuck at
https://wiki.archlinux.org/title/Pi-hole#Set-up_PHP
For security reasons, one can optionally populate the PHP open_basedir directive however, the Pi-hole administration web interface will need access to following files and directories:
/srv/http/pihole
/run/pihole-ftl/pihole-FTL.port
/run/log/pihole/pihole.log
/run/log/pihole-ftl/pihole-FTL.log
/etc/pihole
/etc/hosts
/etc/hostname
/etc/dnsmasq.d/02-pihole-dhcp.conf
/etc/dnsmasq.d/03-pihole-wildcard.conf
/etc/dnsmasq.d/04-pihole-static-dhcp.conf
/var/log/lighttpd/error.log
/proc/meminfo
/proc/cpuinfo
/sys/class/thermal/thermal_zone0/temp
/tmp
I am not able to understand what kind of permission to give rwx or rw- and to user group or to world .
It will be very kind if you help me in this too.
Thanks ,but i actually understand what to do but not how to do, example if i have to provide pi-hole access to /tmp directory ,to whom i provide . Will you please give an example .
[utkarsh@Asus ~]$ ls -l /tmp
total 4
srwxrwxrwx 1 utkarsh utkarsh 0 May 20 13:04 dbus-nyGFOgFdVD
-rw-r--r-- 1 utkarsh utkarsh 0 May 20 13:51 persepolis_exec_utkarsh.lock
drwx------ 2 utkarsh utkarsh 40 May 20 13:04 plasma-csd-generator.VtwUnw
-rw-r----- 1 utkarsh utkarsh 0 May 20 13:04 qipc_sharedmemory_bdedbfdbabcbafb56cd51926635d136055035e4dd9c7d1f5003af98
-rw-r----- 1 utkarsh utkarsh 0 May 20 13:04 qipc_sharedmemory_MSMNotifierforPlasmad7cd3d9ed002d00038761dcd548b1461629c9f02
-rw-r----- 1 utkarsh utkarsh 0 May 20 13:04 qipc_sharedmemory_yWVYQiGRWWoZNvQKvVlWIXZZZbcFFXMreEAQ3ec2a4b8517047ef1abbbd2006e8c4ade795069d
-rw-r----- 1 utkarsh utkarsh 0 May 20 13:04 qipc_systemsem_bdedbfdbabcbafb56cd51926635d136055035e4dd9c7d1f5003af98
-rw-r----- 1 utkarsh utkarsh 0 May 20 13:04 qipc_systemsem_bfcabbfaecebac69dadd18f634141b115a30ce0998c7a1e61e4cfb
-rw-r----- 1 utkarsh utkarsh 0 May 20 13:04 qipc_systemsem_MSMNotifierforPlasmad7cd3d9ed002d00038761dcd548b1461629c9f02
-rw-r----- 1 utkarsh utkarsh 0 May 20 13:04 qipc_systemsem_yWVYQiGRWWoZNvQKvVlWIXZZZbcFFXMreEAQ3ec2a4b8517047ef1abbbd2006e8c4ade795069d
srwx------ 1 sddm sddm 0 May 20 13:03 sddm-:0-hCBGdU
srwxr-xr-x 1 root root 0 May 20 13:03 sddm-auth3c72830d-cd4a-4787-8737-d9fd3e454d6a
drwx------ 3 root root 60 May 20 13:03 systemd-private-e8ac843920d246178e01ab7848fbac54-ModemManager.service-sVHSpi
drwx------ 3 root root 60 May 20 13:03 systemd-private-e8ac843920d246178e01ab7848fbac54-systemd-logind.service-HUga7J
drwx------ 3 root root 60 May 20 13:06 systemd-private-e8ac843920d246178e01ab7848fbac54-systemd-resolved.service-54ZqDO
drwx------ 3 root root 60 May 20 13:04 systemd-private-e8ac843920d246178e01ab7848fbac54-upower.service-anvyAA
drwx------ 2 utkarsh utkarsh 40 May 20 13:51 Temp-01936de7-3d2b-4e48-9b46-03270f15780d
drwx------ 2 utkarsh utkarsh 40 May 20 13:51 Temp-b3695ab0-6d0a-461c-9617-d20d1b2d7cc0
-rw------- 1 utkarsh utkarsh 49 May 20 13:04 xauth-1000-_0
srwx------ 1 utkarsh utkarsh 0 May 20 13:04 'yWVYQiGRWWoZNvQ2K4vVlWI414XZZZbc8FF+XMreEAQ='
