Hi!
Marco> Hi ! I'm studying the error messages returned by the library Marco> and I've some = problems with the following one:
Marco> index element `%s::%s' of row `%s' should but cannot have a Marco> size restriction
Marco> Could someone explain me what does it means and when this error Marco> messages is shown ?
Juergen> OIDs in SNMP are restriced to 128 subidentifier maximum. If Juergen> you index a table by an OID, you will run over the 128 Juergen> subidentifier limit. So the index should have a size Juergen> restriction but the SMI does not allow you to define such a Juergen> size restriction for OIDs.
Juergen> [This seems to be a frequently asked question. Frank, do you Juergen> have time to start a file where we just collect these Juergen> things?]
There is already an explaining desciption in error.c, but just for the case the error message that is shown in case of a local definition. I think, we should just update these texts in error.c instead of starting a new kind of TODO file.
{ 5, ERR_INDEX_OID_NO_SIZE, "index-element-no-size", "index element `%s' of row `%s' should but cannot have a size restriction", "Object identifiers are restricted in size to have at most 128\n" "sub-identifiers. This implies that all index elements used to form\n" "instance identifiers should have a size contraint which ensures\n" "that the 128 sub-identifier constraint is kept intact for any\n" "possible combination of the index elements' values (RFC 2578,\n" "Section 3.5). However the type OBJECT IDENTIFIER cannot formally\n" "be restricted in size (Section 9) although it is legal to use\n" "objects type OBJECT IDENTIFIER as index elements."}, { 5, ERR_INDEX_OID_NO_SIZE_MOD, "index-element-no-size", "index element `%s::%s' of row `%s' should but cannot have a size restriction", NULL},
-frank