Re: screen-4-0-3-logfile-size-0.patch

Jörgen Grahn <[email protected]> Sun, 6 Jul 2008 11:32:32 +0200
Newsgroups gmane.comp.gnu.screen
Message-ID <20080706093231.GJ6641__24665.2311216623$1238089030$gmane$org@tuva.opensoft.se>
[Sorry for breaking the threading. I am not subscribed to
screen-devel, since I don't plan to become more actively involved.]

Solofo wrote:
> On Thu, Jun 26, 2008 at 2:38 AM, Jörgen Grahn
> <address@hidden> wrote:
> > here's a patch which I wrote recently. The reasons and other details
> > (including a short list of potential problems)  [...]
>
> Thanks, nice to see what screen can be useful for!
> Could you explain why you did not choose to use something like ulimit (-f)?

Because it didn't occur to me (even though I think process limits are
an underused Unix feature).

However, I don't think ulimit -f would have worked here -- my screens
have lots of children, and these need to be able to write gigantic
files.  For example, just the *suspicion* that a 1GB core dump could
end up truncated when trying to scp it over for storage would have
been a showstopper.

Hacking screen seemed like a quicker and safer solution. We needed to
raise the 40-window limit anyway, and that's another source code
change.

BR,
/Jörgen

-- 
  // Jörgen Grahn                  | mot du jour: Bobby Driscoll      
\X/ <[email protected]>         |
signature.asc (application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIcJEviVXJlB2Ln/sRAigWAJ0funZFIjXj0Kug1Wo2sjNdcDYe+gCePDnR
+9QBlF1VCY78BX3/RQhvLz4=
=YoTJ
-----END PGP SIGNATURE-----