On 2023/05/16 22:38, Julian Huhn wrote:
> I have an external hard drive that I want to use as a storage
> location for a local mirror. The initial synchronization of the
> mirror went through successfully with openrsync, but each new run
> hangs either with no error or
>Synopsis: Can't sync local usb mounted mirror with openrsync
>Category: system
>Environment:
System : OpenBSD 7.3
Details : OpenBSD 7.3 (GENERIC.MP) #1125: Sat Mar 25 10:36:29 MDT
2023
Hello, sir
My name is Tom. Recently I installed a OpenBSD system at home. And it is
great. I brought a PCI ethernet card, tp-link tg3269c. But I failed to
light it up. Here is data:
ifconfig
re0: flags=8802 mtu 1500
lladdr xx:xx:xx:xx:xx:xx
index 1 priority 0 llprio 3
media: Ethernet none
> Well, then the stategy is not to have a strategy, which is perfectly fine.
The strategy is to teach the principle of not over commiting.
> It still doesn't matter for the use case under discussion here. The "bug"
> reporter expected some OOM type situation, and didn't observe any, because
>
On Tue, 2023-05-16 at 06:33 -0600, Theo de Raadt wrote:
> Rudolf Leitgeb wrote:
>
> > Lots of people (including myself) come from linux background and use
> > OpenBSD for specific security sensitive tasks. Since OpenBSD, like
> > every other desktop OS these days, has some strategy to deal
> >
Theo de Raadt wrote:
> Rudolf Leitgeb wrote:
>
> > Lots of people (including myself) come from linux background and use
> > OpenBSD for specific security sensitive tasks. Since OpenBSD, like
> > every other desktop OS these days, has some strategy to deal
> > with OOM conditions, the term
Rudolf Leitgeb wrote:
> Lots of people (including myself) come from linux background and use
> OpenBSD for specific security sensitive tasks. Since OpenBSD, like
> every other desktop OS these days, has some strategy to deal
> with OOM conditions, the term "OOM killer" is perfectly clear
>
On Tue, 2023-05-16 at 09:16 +0100, Stuart Henderson wrote:
> The strategy is that the sysadmin should configure datasize limits so
> that processes hit memory allocation failures if they try to
> overreach.
> Defaults are setup with typical use-cases and machines in mind but
> you
> might know
On 2023/05/16 09:12, Rudolf Leitgeb wrote:
> Lots of people (including myself) come from linux background and use
> OpenBSD for specific security sensitive tasks. Since OpenBSD, like
> every other desktop OS these days, has some strategy to deal
> with OOM conditions, the term "OOM killer" is
Lots of people (including myself) come from linux background and use
OpenBSD for specific security sensitive tasks. Since OpenBSD, like
every other desktop OS these days, has some strategy to deal
with OOM conditions, the term "OOM killer" is perfectly clear
regardless of what the actual
10 matches
Mail list logo