[1869] in Moira
RE: blank winshell field
daemon@ATHENA.MIT.EDU (Paul B. Hill)
Mon Oct 1 14:07:16 2001
From: "Paul B. Hill" <pbh@MIT.EDU>
To: <bug-moira@mit.edu>
Date: Mon, 1 Oct 2001 14:05:14 -0400
Message-ID: <JDEEIOCIIGMKDNGJMBLJEEIKCIAA.pbh@mit.edu>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
In-Reply-To: <200110011447.KAA12223@geskekelud.mit.edu>
Hi,
Why is the windows shell entry a mandatory non-null field? Our intent was
that null be allowed, in this case the default shell would be used.
-----Original Message-----
From: Laura Baldwin [mailto:boojum@MIT.EDU]
Sent: Monday, October 01, 2001 10:47 AM
To: bug-moira@MIT.EDU
Subject: blank winshell field
So this isn't a stanley bug, more of a data bug:
stanley danutek -cl GUEST03M
gave me "stanley: DBMS system error occurred while updating user."
and the zephyr to -c moira said something about a mandatory non-null
field being null. It turns out his windows shell entry was set to
null, so nothing else could be updated while that was the case. I
set it back to cmd, and forgot to look at the last-modified-by, but
the moira backup locker seems to suggest it was reg_svr, so I don't
know where the blank came from.
-Laura
