From BARRYG at MIT-MC  Tue Dec 23 00:00:00 1980
From: BARRYG at MIT-MC (BARRYG at MIT-MC)
Date: 23 Dec 1980 00:00
Subject: No subject
Message-ID: <mailman.730.1479821117.4695.its@nocrew.org>

I would appreciate it if someone would, at your leisure, restore
MC:GUEST0;BARRYG XMAIL from whatever backups are maintained.
	/barry

From RWKatMIT-MC  Mon Dec 22 00:00:00 1980
From: RWKatMIT-MC (Robert W. Kerns)
Date: 22 December 1980, 00:00
Subject: No subject
Message-ID: <mailman.731.1479821117.4695.its@nocrew.org>

    Date: 22 December 1980 00:00-EST
    From: Kent M. Pitman <KMP at MIT-MC>
    To: RWK at MIT-MC, BUG-ITS at MIT-MC, USER-ACCOUNTS at MIT-MC
    cc: MLK at MIT-MC, ELLEN at MIT-MC

        Date: 21 December 1980 09:17-EST
        From: Michael L. Kazar <MLK>
        To:   USER-ACCOUNTS

        Some twerp just enslaved my terminal and $$U'ed me off. It was from
        a vadic dialup no less! May I suggest that maybe PWORD should
        not allow enslaves but only links. ??
    -----
    Would it be hard to set things up so that ^_E was disallowed from PWORD?
    Unlogged DDTs could also do it if it's easier to check uname than jname.
    Anyway, some unlogged random slaved a Macsyma user and lost him a lot of 
    work the other day and he was quite upset.

    If this can't be done, I recommend that for the safety of our paying users,
    initiating links from unlogged pwords should be made impossible. This is,
    however, a more extreme measure than I would like to take if we can help
    it, though.

    Thanks. -kmp

This has also happened several times recently on ML, and ML's PWORD is
currently patched to disallow initiating links.  But better than this would be
to have ^_E not work on a not-logged-in dialup or STY (leaving local TTY's
alone).  This is a simple change to ITS, and minimizes the restrictions imposed
to achieve the goal.  If there are no objections I'm willing to do the
(trivial) work.


From KMPatMIT-MC  Mon Dec 22 00:00:00 1980
From: KMPatMIT-MC (Kent M. Pitman)
Date: 22 December 1980, 00:00
Subject: No subject
Message-ID: <mailman.732.1479821117.4695.its@nocrew.org>

    Date: 21 December 1980 09:17-EST
    From: Michael L. Kazar <MLK>
    To:   USER-ACCOUNTS

    Some twerp just enslaved my terminal and $$U'ed me off. It was from
    a vadic dialup no less! May I suggest that maybe PWORD should
    not allow enslaves but only links. ??
-----
Would it be hard to set things up so that ^_E was disallowed from PWORD?
Unlogged DDTs could also do it if it's easier to check uname than jname.
Anyway, some unlogged random slaved a Macsyma user and lost him a lot of 
work the other day and he was quite upset.

If this can't be done, I recommend that for the safety of our paying users,
initiating links from unlogged pwords should be made impossible. This is,
however, a more extreme measure than I would like to take if we can help
it, though.

Thanks. -kmp


From GJC at MIT-MC  Fri Dec 19 00:00:00 1980
From: GJC at MIT-MC (GJC at MIT-MC)
Date: 19 Dec 1980 00:00
Subject: No subject
Message-ID: <mailman.733.1479821117.4695.its@nocrew.org>

I'm not sure exactly who to complain to on this,
I've complained about the bugginess of H19WHO many times
before. Anyway, there is a DSN's tree with a running
H19WHO on it now on MC which has used up 2 hours of CPU time.
I've just :ujob jmsk hactro and :snarfed the job, and it
significantly improves the fair share.

This problem comes up very often when a user with an
h19who gets detached. As soon as I reowned the tree
the h19who typed out on my tty and stopped burning up cpu time.
When ^X'd it was doing a .HANG
...now, how is it that you save jobs for examination??


From FJWatMIT-MC  Fri Dec 19 00:00:00 1980
From: FJWatMIT-MC (Frank J. Wancho)
Date: 19 December 1980, 00:00
Subject: Access to AI via DARCOM PTIP
Message-ID: <mailman.734.1479821117.4695.its@nocrew.org>

Attempts to connect to AI from the DARCOM-PTIP are met with "ITS being
Debugged" when, in fact, it is not.  I understand that the same
message is sent when attempting to connect from other TIPs in the D.C.
area.  If you are trying to block randoms and are having trouble
specifically with DARCOM-PTIP users, I would like to have the details
so corrective action can be taken and the block can be removed.  If
not, then please remove the block.

Thanks,
Frank


From MoonatCADR16 at MIT-MC  Tue Dec 16 00:00:00 1980
From: MoonatCADR16 at MIT-MC (MoonatCADR16 at MIT-MC)
Date: 16 Dec 1980 00:00
Subject: No subject
Message-ID: <mailman.735.1479821117.4695.its@nocrew.org>

This sounds unlikely.  File authors are stored as the disk address of the
user's home directory.  No name parsing is involved.  (The reason they are stored
this peculiar way is because whoever put them in couldn't find enough bits to
store a sixbit name.)

From CWH at MIT-MC  Tue Dec 16 00:00:00 1980
From: CWH at MIT-MC (CWH at MIT-MC)
Date: 16 Dec 1980 00:00
Subject: No subject
Message-ID: <mailman.736.1479821117.4695.its@nocrew.org>

If the userid contains a numeric digit as a character in the middle of the
name, only the alphabetic characters preceding the digit are looked at when
setting the file author.  For instance, if a file is created by uname
K7X, the file author is shown to be K.


From GJC at MIT-MC  Fri Dec 12 00:00:00 1980
From: GJC at MIT-MC (GJC at MIT-MC)
Date: 12 Dec 1980 00:00
Subject: No subject
Message-ID: <mailman.737.1479821117.4695.its@nocrew.org>

MC appears to be crashing somewhat harder
than I've ever seen an ITS system do.
I have had files written out, e.g. GJC;FOO 1
a few minutes ago, and even compiled,
so I *know* is was there, and then
MC crashes, and when I get back 5 minutes
later the file is *gone*.

ouch.



From JLK  Thu Dec 11 00:00:00 1980
From: JLK (John L. Kulp)
Date: 11 DEC 1980, 00:00
Subject: No subject
Message-ID: <mailman.738.1479821117.4695.its@nocrew.org>

MLDEV SEEMS TO BE TRUNCATING FILES.  I JUST DID :COPY ON MC OF
MC:DATDRW;WL BIN TO AI:
AND THE FILE ON AI WAS NICELY ROUNDED OFF TO EXACTLY 72 BLOCKS
(THE ACTUAL FILE IS 72 AND 709 WORDS).

From RWK at MIT-MC  Mon Dec  8 00:00:00 1980
From: RWK at MIT-MC (RWK at MIT-MC)
Date: 08 Dec 1980 00:00
Subject: CORBLK: NO CORE AVAILABLE
Message-ID: <mailman.739.1479821118.4695.its@nocrew.org>

That means there is no more virtual memory left in the system.  I.e. there
are too many people using the system to get anything done.  The best thing
to do is to go away for a while.  Baring that, you can always just $P it again.
When there is enough core, it will continue where it was.  It may take a while,
the easiest way to get some core freed up is to log out.  There's lots of other
people trying to get to any newly freed core before you.


From RAM at MIT-MC  Mon Dec  8 00:00:00 1980
From: RAM at MIT-MC (RAM at MIT-MC)
Date: 08 Dec 1980 00:00
Subject: No subject
Message-ID: <mailman.740.1479821118.4695.its@nocrew.org>

running nbabyl i got:

ERROR CORBLK: NO CORE AVAILABLE
15243>>.CALL 37607 (CORBLK)


From RWKatMIT-MC  Sat Dec  6 00:00:00 1980
From: RWKatMIT-MC (Robert W. Kerns)
Date: 6 December 1980, 00:00
Subject: File Authors
Message-ID: <mailman.741.1479821118.4695.its@nocrew.org>

    Date: 6 DEC 1980 0616-EST
    From: JONL at MIT-MC (Jon L White)
    To:   (BUG ITS) at MIT-MC
    cc:   RWK at MIT-MC, (BUG DDT) at MIT-MC
    Re:   File Authors

    :MOVE <foo>, <bar>
    fails to preserve the file's author field.
Not true!  You're being confused by EMACS's DIRED, which displays the bug.

From JONL at MIT-MC  Sat Dec  6 00:00:00 1980
From: JONL at MIT-MC (JONL at MIT-MC)
Date: 06 Dec 1980 00:00
Subject: File Authors
Message-ID: <mailman.742.1479821118.4695.its@nocrew.org>

:MOVE <foo>, <bar>
fails to preserve the file's author field.


From ___010 at MIT-AI  Thu Dec  4 00:00:00 1980
From: ___010 at MIT-AI (___010 at MIT-AI)
Date: 04 Dec 1980 00:00
Subject: No subject
Message-ID: <mailman.743.1479821118.4695.its@nocrew.org>

Gee, MC hasn't been very reliable lately, crashed again now...