![]() | |||||||||||||
Messages in this thread |
Hi. >>>>>there is one. Nothing uses it >>>>>(sysconf() provides this info) >>>> >>>>Seems to me that it would be fairly trivial to modify those programs >>>>(that should use this mechanism but don't) to use it? So why should >>>>they be allowed to dictate kernel behaviour? >>> >>> >>>quality of implementation; for example shell scripts that want to do >>>echo 500 > /proc/sys/foo/bar/something_in_HZ >>>... >>>or /etc/sysctl.conf or ... >>> >> >>Then write a simple program already. How hard is it to write a program >>that does a sysconf() and returns (as ascii of course) just the >>value of HZ? Then do some trivial calculation off of that. > > > How about a slightly more useful utility, like this: > > $ getconf CLK_TCK > 100 > $ getconf OPEN_MAX > 1024 > $ getconf PATH_MAX /proc/ > 4096 > $ Yes, yes, yes, I like that one actually. It does solve the shell script issues and we've never said that things don't need to adapt to changes before so I don't see why not now. And that one would be good to have regardless of the HZ issue. // Stefan - 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/ | ||||||||||||
| Last update: 2005-03-22 13:01 [from the cache] ©2003-2008 | |||||||||||||