From: Scott Schwartz <schwartz@galapagos.cse.psu.edu>
To: Sam Fans <sam-fans@hawkwind.utcs.toronto.edu>
Subject: MAXFILES, ouch!
Date: Wed, 15 Mar 1995 02:45:16 -0500 [thread overview]
Message-ID: <95Mar15.024517est.12684@galapagos.cse.psu.edu> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 333 bytes --]
void
menuins(int n, uchar *s, Text *t, int m, int tg)
{
int i;
if(nname == MAXFILES)
panic("menuins");
Panic? Ouch! That's a pretty harsh penalty for a software tool to
exact for exceeding arbitrary limits. (perror then gets to say
"Not a tty", or the local equivalent, just before samterm stops
being a tty. ☺)
reply other threads:[~1995-03-15 7:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=95Mar15.024517est.12684@galapagos.cse.psu.edu \
--to=schwartz@galapagos.cse.psu.edu \
--cc=sam-fans@hawkwind.utcs.toronto.edu \
/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).