If I run cbqinit on my own it works fine. If I run the init.d script, though, I get varying results. Most common is [!!] error indication, incorrectly returned because it appears cbqinit returns a non-0 error status if there is already cached info. running cbqinit start invalidate instead of cbqinit start solves that problem. Also, I get: xargs: environment is too large for exec **CBQ: failed to compile CBQ configuration! If I attempt to run the init.d script. Again, cbqinit runs fine on its own.
update your baselayout *** This bug has been marked as a duplicate of 23569 ***
Please note there are two parts to this bug. The xargs, and the fact that when cbqinit is caching, the init.d script does not realise it still worked - needs to check for the cache errno status.
Hm. Take that back, perhaps I was just confusing symptoms. Have just started and stopped cbqinit a few times from commandline and no status 127 I thought I saw before. Won't hassle about reopening unless I see that again :)
