When it runs from there it malfunctions but I can't see anything in the log. First how do I get it's errors visible in the log? and second any idea what could be wrong. I do know the script is running but the files it writes variables to are all blank. Here is the code https://pastebin.com/GJafHTY1
#sets script dir as working dir
cd "$(dirname "$0")"
Joined: 16 Nov 2015 Posts: 4805 Location: UK, London, just across the river..
Posted: Mon Oct 18, 2021 4:34 Post subject:
i guess you did make it executable ??
chmod +x script path
and where exactly it should store its stuff in opt?
apart of tmp that doesn't survive reboot and opt that is on usb and survives reboot the other fs is ready only…. _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 48081 AP,NAT
TP-Link WR1043NDv2 -DD-WRT 47900 AP,NAT,AP Isolation,Ad-Block,Firewall,Local DNS,Forced DNS,DoT,VPN,VLAN
TP-Link WR1043NDv2 -DD-WRT 48081 AP,NAT,Ad-Block,Firewall,Local DNS,Forced DNS,DoT,VPN,VLAN
TP-Link WR1043NDv2 -Gargoyle OS 1.13.0b AP,NAT,QoS,Quotas
Netgear R7800 --DD-WRT 48081 AP,NAT,AD-Block,AP&Net Isolation,VLAN's,Firewall,Local DNS,DoT,Vanilla
Netgear R9000 --DD-WRT 48081 AP,NAT,AD-Block,AP Isolation,Firewall,Local DNS,DoT,2,4Ghz only,Vanilla
Netgear R7000 ---DD-WRT 48081 AP,Wi-Fi OFF,NAT,AD-Block,Firewall,Local DNS,Forced DNS,VLAN's,DoT,VPN
Stubby for DNS over TLS I DNSCrypt v2 by mac913
Last edited by Alozaros on Mon Oct 18, 2021 7:43; edited 1 time in total
. This showed me the error in that txt file. Searching here found that cron and presumable startup don't share the same PATH as telnet. I used
to see the cron PATH '/usr/bin:/bin:/sbin:/usr/sbin:/jffs/sbin:/jffs/bin:/jffs/usr/bin:/jffs/usr/sbin' which is quite limited compared to telnet's '/bin:/usr/bin:/sbin:/usr/sbin:/jffs/sbin:/jffs/bin:/jffs/usr/sbin:/jffs/usr/bin:/mmc/sbin:/mmc/bin:/mmc/usr/sbin:/mmc/usr/bin:/opt/sbin:/opt/bin:/opt/usr/sbin:/opt/usr/bin'. I am surprised all those are needed when /opt/bin is where every installed package goes and that the other path doesn't have that added. Kind of a stupid lack of a feature.
Would be nice if the syslog showed the script outputs and errors too.