Messages in this thread |  | | Date | Wed, 05 Sep 2001 11:56:00 -0700 | From | Tim Hockin <> | Subject | sysctl() strategy questions |
| |
All,
I've noticed an anomaly, and am not sure which behavior is correct:
sysctl_string() stores the value it reads to table->data sysctl_intvec() validates but does not store the value it reads
whereas
proc_intvec() does store the intvec it reads, but does not validate proc_dostring() stores the string it read
Should sysctl_intvec() be storing the data, or should sysctl_string() NOT? Or is this oddness by design?
Also, what is the typical answer to a sysctl variable that is essentially an enum? Ideally the /proc interface can show it as a meaningful string, but should the sysctl() interface pass the integer values (cleaner)? Should I toss an enum into sysctl.h ?
Tim -- Tim Hockin Systems Software Engineer Sun Microsystems, Cobalt Server Appliances thockin@sun.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |