From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: 9front@9front.org
Subject: I fork-bombed my system
Date: Mon, 22 Jun 2015 17:12:52 +0100 [thread overview]
Message-ID: <20150622171252.3487a836@lahti.ethan.home> (raw)
The script below turned out to be a fork-bomb. The fix was simple, but
a little obscure. Anyone want to figure out what it was? :)
#!/bin/rc
fn midac {
window -r 323 0 969 663 ac $*
}
if(~ $1 -@){
window -r 0 0 444 444 # top left
window -r 848 0 1292 444 # top right
window -r 0 440 648 884 # bottom left
window -r 644 440 1292 884 # bottom right
midac $home/games/CURRENT
midac $home/src/00CURRENT
exit
}
if(~ $1 '-#'){
plumber
exec rio -i $0^' -@'
}
exec w $0 '-#'
next reply other threads:[~2015-06-22 16:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 16:12 Ethan Grammatikidis [this message]
2015-06-22 16:15 ` [9front] " Glauco Rocha
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=20150622171252.3487a836@lahti.ethan.home \
--to=eekee57@fastmail.fm \
--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).