From: thinktankworkspaces@gmail.com
To: 9front@9front.org
Subject: Re: [9front] rewrite gateway
Date: Fri, 28 Jan 2022 13:10:04 -0800 [thread overview]
Message-ID: <BF8A64B24AF2C978FB7987377FC17DFF@gmail.com> (raw)
In-Reply-To: <5489EE48FB95006A7BB9588005F54AC9@felloff.net>
[-- Attachment #1: Type: text/plain, Size: 282 bytes --]
This is extremely hard to troubleshoot. I tried both mk install and mk safeinstall,
rebooted twice and the problem still persists.
Its unusable. I'm not familiar enough with the command line version to debug further.
I also tried to make sure upas/fs was not running as well.
[-- Attachment #2: Type: message/rfc822, Size: 3499 bytes --]
From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] rewrite gateway
Date: Fri, 28 Jan 2022 20:07:12 +0100
Message-ID: <5489EE48FB95006A7BB9588005F54AC9@felloff.net>
this can happen with any program that you override its binary while
it is running.
the text/data is demand paged, which means that under memory pressure,
the kernel will discard the pages and on demand read it back from the
file again.
just reboot after a mk install, or use mk safeinstall (which renames
the file before copying avoiding the override in place).
btw, ori's new filesystem might have a experimental feature trying to
make snapshots of the while when they'r opend with OEXEC flag avoiding
this issue.
--
cinap
next prev parent reply other threads:[~2022-01-28 21:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 0:52 thinktankworkspaces
2022-01-28 19:07 ` cinap_lenrek
2022-01-28 21:10 ` thinktankworkspaces [this message]
2022-01-28 21:22 ` ori
2022-01-28 23:04 ` thinktankworkspaces
2022-01-29 13:14 ` hiro
2022-01-29 14:18 ` cinap_lenrek
2022-01-29 20:50 ` cinap_lenrek
2022-01-29 23:29 ` thinktankworkspaces
2022-01-29 23:40 ` thinktankworkspaces
2022-01-30 12:14 ` cinap_lenrek
2022-01-30 16:16 ` ori
2022-01-30 23:01 ` thinktankworkspaces
2022-01-29 14:29 ` cinap_lenrek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BF8A64B24AF2C978FB7987377FC17DFF@gmail.com \
--to=thinktankworkspaces@gmail.com \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).