Could someone clarify why the nvargus-daemon.service require the network-online.target as its dependency? We saw it hanging on a system that wasn’t online making the camera startup to be delayed. Are there any issues with removing this dependency? Here are the contents of the service configuration /etc/systemd/system/nvargus-daemon.service
[Unit]
Description=Argus daemon
; Everything depends on the NVIDIA per-boot script
After=nv.service
; TPC power gating must be enabled before anything touching gpu
After=nvpmodel.service
After=network-online.target
Wants=network-online.target
[Service]
Type=simple
ExecStart=/usr/sbin/nvargus-daemon
StandardOutput=syslog
Restart=on-failure
[Install]
WantedBy=multi-user.target
as you can see… $ ls /usr/lib/aarch64-linux-gnu/tegra/libnvargus* libnvargus.so libnvargus_socketclient.so libnvargus_socketserver.so
and…
here’s the socket used for initial connection to the Argus daemon, i.e. /tmp/argus_socket
when Argus server started, it will listen on the unix domain socket for connection requests.
I will add that “networking” includes the loopback address. Loopback is a virtual address tied to the local system (indeed, you can either “ping localhost” or “ping 127.0.0.1”). It is quite possible that you don’t need any other part of the network. Note that if this is the case, then even if there is no wired or wireless network, it would still work (but it would still bring up and make available localhost).