From: Nathan T. <er...@cs...> - 2005-04-13 02:08:30
|
John, > My worries about virtualizing the daemonrc location is that daemonrc is > very much an implementation detail: it can change, or disappear at will. > I don't want to encourage people to believe the file is directly > editable, because it isn't. > > Also, it's worth noting that this config file is user-specific. It's not > at all a stretch to image ~toor/.oprofile/daemonrc etc. > > You must have some method of enabling oprofile on the nodes in the first > place: in that case, isn't it equally possible that that method also > includes the opcontrol invocations you need to configure? I suppose > you'd still need a /root/.oprofile/ in your RAM disk for this situation > but I don't see that as a big burden. > > If I'm misunderstanding something here, let me know - if it proves to be > really needed, then we could consider an environment variable locating > the daemonrc. But I'd rather not do that right now. You are correct that the /root/.oprofile issue is not difficult to work around. All it requires is a 'mkdir /root' in the RAM disk. (At least, I haven't noticed any requirement other than this yet.) -Nathan. |