If it were me, I'd probably create an
/etc/sysfs.conf, and an
/etc/init.d/sysfsutils init script. Then I could keep all of my sysfs related configs and options separate from everything else. With an init script, it could be managed and handled using the standard idioms for managing services and configurations through SysV init scripts (including
service sysfsutils [start|stop|reload|restart|status] on RHEL/CentOS (with a little extra work)).
Even if I didn't bother with the
/etc/init.d/sysfsutils script, I'd still put the options into
/etc/sysfs.conf and then call/process the contents of that file from a separate script (
/etc/rc.local, as a last/lazy option).
Note: Debian and Debian-based distributions (Ubuntu, etc.) already do this, and ship an
/etc/sysfs.conf config file and init script with their sysfsutils package. Grabbing those two files from a Debian/Ubuntu box (or the Debian source package for sysfsutils) would probably be a good way to start for replicating it yourself.