Endeover:
In 7.3, I end up starting also unbound service by rcctl instead of
unbound-control (losing maybe something about security) hoping to give me a
better
general standard to control my services, including my approach
to sysupgrade.
Thanks to everyone who reply in the thread.
--
Thanks Steve.
Jul 30, 2023 00:07:35 Steve Litt :
> I use runit (on Void Linux) every day, and love it to death. Runit is
> extremely simple. S6 is a little more capable and a little more complex.
Thank you for all the hints, expecially about runit, I didn't know it.
I'm going trying to fix
Daniele B. said on Tue, 25 Jul 2023 16:33:50 +0200 (GMT+02:00)
>My unattended upgrade happend like that:
>
>- I took up unbound
>- sysupgrade
>- 1st fw_update (this probbly is okay)
>- reboot
>- installation of the sets
>- 2nd fw_update (this fails because unattended, local Unbound is down)
>-
On Jul 28, 2023 20:00:24 I was still sleeping when suddenly Paul said:
> If you really want to go without DNS resolution, I invite you to
> travel back a few decades and learn about /etc/hosts.
did you hear my
"True, the hosts.. Oh Jesus!"... ?
Many thx! :D
-- Daniele Bonini
I don't understand - if you configure your system to not have working
DNS resolution, then you will not have working DNS resolution.
fw_update needs working DNS resolution, so yeah .. if you break the
latter, you break the former.
Don't break DNS resolution. You really get what you pay for.
My unattended upgrade happend like that:
- I took up unbound
- sysupgrade
- 1st fw_update (this probbly is okay)
- reboot
- installation of the sets
- 2nd fw_update (this fails because unattended, local Unbound is down)
- reboot
- 3rd fw_update (this fails because unattended, local Unbound is
Thanks Steve,
Jul 25, 2023 14:41:53 Steve Litt :
> chattr -i resolv.conf && echo nameserver 8.8.8.8 >> resolv.conf && chattr +i
> resolv.conf
>
> I also don't understand why you start unbound manually instead of from
> computer initialization. It sounds like if unbound started before
>
Daniele B. said on Tue, 25 Jul 2023 11:29:09 +0200 (GMT+02:00)
>Hello Stuart, thanks for this one..
>
>Yes, I agree that the final solution could be only the replace my
>listed nameserver. But do you remember I was using also the unmutable
>flag on resolv.conf ? :D
chattr -i resolv.conf &&
Hello Stuart, thanks for this one..
Yes, I agree that the final solution could be only the replace my listed
nameserver.
But do you remember I was using also the unmutable flag
on resolv.conf ? :D
I do not want to awake the lions and indeed I'm much happy about
my *unbound system* but
On 2023-07-25, Daniele B. wrote:
>
> Hello,
>
> Just coming from my fresh upgrade to OpenBSD 7.3 and thanks again for
> it.. ;)
>
> No particular problem except my realization that with my settings
> (unbound started manually) fw_update goes to fail (all the three
> attempts) on each (unattended)
Hello,
Just coming from my fresh upgrade to OpenBSD 7.3 and thanks again for
it.. ;)
No particular problem except my realization that with my settings
(unbound started manually) fw_update goes to fail (all the three
attempts) on each (unattended) upgrade. If fw_update happens to be a
11 matches
Mail list logo
