Re: Segmentation fault / firefox (core dumped)

>> Have you tried increasing datasize-cur and -max under "default:\" >> in /etc/login.conf ? I have mine set to 2048M > >I have 512 MB there. My computer has 1024MB Ram. It will be slow, but you can increase datasize beyond physical RAM. How much swap space do you have? You can use swapctl to

Re: wxallowed flag

I think you have interpreted the situation backwards. The wxallowed flag is not on other filesystems. Therefore, binaries on those filesystems which misbehave will fail. There are about 15 programs which need fixing, and the wxallowed could become a piece of history. Unfortunately some of

Re: Segmentation fault / firefox (core dumped)

Fri, 26 Jan 2018 00:26:11 + (GMT) Roderick > I get continously this and other errors. In OpenBSD, in FreeBSD. > > I think it is time to change browser, but I distrust chrome as comming > from data collector google. > > The problem is that those that make WEB pages decide

on-line kernel debugging

Hi! does OpenBSD supports on-line kernel debugging as FreeBSD does[1]? The only tutorial I managed to find was a fairly old one[2] by QEMU over GNU/Linux but it seems kgdb(7) is removed since 6.2 (apparently for not even working before[3]). Thank you! [1]:

Re: Unexpected security(8) output

Hi Clint, Clint Pachl wrote on Fri, Jan 26, 2018 at 10:43:47AM -0700: > I received the following output from security(8): > > Running security(8): > Can't > opendir(/home/pachl/.cache/mozilla/seamonkey/e8cxa4g0.default/safebrowsing-backup): > No such file or directory at /usr/libexec/security

Re: Unexpected security(8) output

On Fri, Jan 26, 2018 at 10:43:47AM -0700, Clint Pachl wrote: > I received the following output from security(8): > > Running security(8): > Can't > opendir(/home/pachl/.cache/mozilla/seamonkey/e8cxa4g0.default/safebrowsing-backup): > No such file or directory at /usr/libexec/security line 594.

Re: Segmentation fault / firefox (core dumped)

On Fri, 26 Jan 2018 17:50:02 + > On Fri, 26 Jan 2018 17:13:47 + (GMT) > > > > (1) "even *running* firefox on an i386 netbook with 1Gb of memory > > is unbearable." > > We still have a 1.73 Ghz 1.5 Gigabyte Ram laptop that does OK with > firefox. It is running fvwm 1 as a desktop

Re: Segmentation fault / firefox (core dumped)

You can try Otter-browser. It is a fork of the Opera browser. My bank website and a few other websites refuse secure logins but in general it works well. I am using it on OpenBSD 6.1. It won't play videos until you install the necessary plugins. Here is how to fix it. >Description: The

Re: Segmentation fault / firefox (core dumped)

On Fri, 26 Jan 2018 17:13:47 + (GMT) > (1) "even *running* firefox on an i386 netbook with 1Gb of memory is > unbearable." We still have a 1.73 Ghz 1.5 Gigabyte Ram laptop that does OK with firefox. It is running fvwm 1 as a desktop though which requires clicks occasionally for some

Re: Segmentation fault / firefox (core dumped)

On Fri, 26 Jan 2018 11:10:45 -0500 > > I have 512 MB there. My computer has 1024MB Ram. For what does > > firefox need so much memory?! I think that puzzles everyone. Browsers are often full of memory leaks too. I haven't had any crashes on 57 or 58 btw. I haven't checked quantum but priorly

Unexpected security(8) output

I received the following output from security(8): Running security(8): Can't opendir(/home/pachl/.cache/mozilla/seamonkey/e8cxa4g0.default/safebrowsing-backup): No such file or directory at /usr/libexec/security line 594. I didn't realize security parses through user files; beyond a few dot

Re: Segmentation fault / firefox (core dumped)

> > > I only need a browser. > > > > Surf? w3m? > > w3m is a phantastic tool! When it gets unbearable, I copy the location > from firefox and feed w3m with it. > > I will try later surf. > > iridium does not convince me till now. It seems to be a new browser > (different from chrome) as any

Re: Segmentation fault / firefox (core dumped)

On Fri, 26 Jan 2018, Allan Streib wrote: > Mine is set to 2048M also. I almost never have Firefox crashes > esp. on newer builds from Landry Breuil as described here: > > https://undeadly.org/cgi?action=article=20170425173917 (1) "even *running* firefox on an i386 netbook with 1Gb of memory

Re: Segmentation fault / firefox (core dumped)

Roderick writes: > On Thu, 25 Jan 2018, meg...@r53sound.com wrote: > >> Have you tried increasing  datasize-cur and -max under "default:\" >> in /etc/login.conf ? I have mine set to 2048M > > I have 512 MB there. My computer has 1024MB Ram. For what does firefox > need so much

Re: gzip compression and httpd/relayd

On 2018-01-25, Thuban wrote: > I'm very happy with relayd + httpd. > Relayd deals with headers and httpd serve files. > > I know httpd doesn't have gzip compression. > > 1. Do you know if it's planned in the future? https://github.com/reyk/httpd/issues/21

Re: wxallowed flag

Well, I've just checked python's port and created a package without USE_WXNEEDED and it works pretty well. How about I'll send a patch to ports@ which will create "wx" or "no_wx" flavor?

Re: IPsec help: too much NAT!

When faced with an ISP modem/router, I generally try to switch it to bridge mode and move the PPPoE / DHCP client formerly handled by the ISP hardware to the OpenBSD system instead. This rather simplifies things if you can make it work because then your OpenBSD system has the Internet-facing

Re: nat-to (least-states / round-robin) problem

On 23/01/18 11:54, Kapetanakis Giannis wrote: > On 23/01/18 11:08, Kapetanakis Giannis wrote: >> Hi, >> >> I've discovered something that looks like a bug in nat translation with >> least-states or round-robin >> >> Instead of using the nat-pool is uses wrong IPs >> >> # pfctl -sr -R0 >> pass out

Re: wxallowed flag

On Fri, Jan 26, 2018 at 01:52:10PM +0200, mazocomp wrote: > On Fri, Jan 26, 2018 at 12:28:00PM +0100, Marc Espie wrote: > > On Fri, Jan 26, 2018 at 12:56:15PM +0200, mazocomp wrote: > > > Hi! > > > > > > Is this a really good idea to keep wxallowed flag on /usr/local by > > > default? Is this so

Re: wxallowed flag

Le 2018-01-26 12:52, mazocomp a écrit : On Fri, Jan 26, 2018 at 12:28:00PM +0100, Marc Espie wrote: On Fri, Jan 26, 2018 at 12:56:15PM +0200, mazocomp wrote: > Hi! > > Is this a really good idea to keep wxallowed flag on /usr/local by > default? Is this so scary that many poop software will

Re: wxallowed flag

On Fri, Jan 26, 2018 at 12:28:00PM +0100, Marc Espie wrote: > On Fri, Jan 26, 2018 at 12:56:15PM +0200, mazocomp wrote: > > Hi! > > > > Is this a really good idea to keep wxallowed flag on /usr/local by > > default? Is this so scary that many poop software will break (this is > > not a big loss

Re: wxallowed flag

On Fri, Jan 26, 2018 at 12:56:15PM +0200, mazocomp wrote: > Hi! > > Is this a really good idea to keep wxallowed flag on /usr/local by > default? Is this so scary that many poop software will break (this is > not a big loss at all)? After all not enabling this flag by default is > the right thing

Re: Segmentation fault / firefox (core dumped)

On Thu, 25 Jan 2018, meg...@r53sound.com wrote: > Have you tried increasing  datasize-cur and -max under "default:\" > in /etc/login.conf ? I have mine set to 2048M I have 512 MB there. My computer has 1024MB Ram. For what does firefox need so much memory?! And seemonkey seems to be more

wxallowed flag

Hi! Is this a really good idea to keep wxallowed flag on /usr/local by default? Is this so scary that many poop software will break (this is not a big loss at all)? After all not enabling this flag by default is the right thing to do, reliance on W|X should go to /dev/null The only problem I see

Re: gzip compression and httpd/relayd

On Thu, Jan 25, 2018 at 09:37:06PM +0100, Michael Hekeler wrote: > Am Thu, 25 Jan 2018 19:47:09 +0100 > schrieb Thuban : > > > I'm very happy with relayd + httpd. > > Relayd deals with headers and httpd serve files. > > > > I know httpd doesn't have gzip compression. > >