[1022] in Moira

home help back first fref pref prev next nref lref last post

Re: moira field lengths

daemon@ATHENA.MIT.EDU (Marc Horowitz)
Mon Nov 11 09:47:29 1996

To: danw@MIT.EDU (Dan Winship)
Cc: moiradev@MIT.EDU, moira-admin@MIT.EDU, accounts@MIT.EDU
From: Marc Horowitz <marc@cygnus.com>
Date: 11 Nov 1996 09:47:18 -0500
In-Reply-To: danw@MIT.EDU's message of Sun, 10 Nov 1996 17:00:17 -0500 (EST)

danw@MIT.EDU (Dan Winship) writes:

>> So, are there any fields that people think are too short now and ought
>> to be lengthened?

Is the user shell length still 32?  This should be at least 64, and if
the database rep is efficient, MAXPATHLEN.

>> Also, a poll: currently, moira silently truncates any arguments that
>> are too long to fit into the database. It would be trivial to change
>> this to make it return an error message instead. (The error number
>> [MR_ARG_LEN] is already defined, but it's only returned in certain
>> esoteric circumstances.) Do people think that would be a Good Thing or
>> a Bad Thing? (Or good in some cases, but bad in others.) This would be
>> something that would happen sometime after the switchover if it did
>> happen.

I think it would be good.  At worst, we can have the clients catch
this error, and feed back a truncated string if we want to keep that
behavior in some clinet.  There is a way to get the max length for a
field in the protocol, or at least in the error, right?

		Marc

home help back first fref pref prev next nref lref last post