[nas] 2 possible patches for the 1.9.1 version
jon at radscan.com
Tue Nov 6 11:35:14 MST 2007
On Fri, 2 Nov 2007, Raymond Toy (RT/EUS) wrote:
> Frank Büttner wrote:
>> Jon Trulson schrieb:
>>> This one I am not sure about either... It does sound like a good
>>> idea, but:
>>> - Is this the generally accepted practice for linux now? Should we
>>> '#if defined(linux)' it?
>>> - looking briefly, it looks like at least Solaris 10 also does the
>>> /var/run thing... Are there any Solaris people that think this
>>> should be done on that platform by default too?
>>> - *BSD's? What are they doing these days?
>>> I don't want to add this particular patch as-is (at least for 1.9.1)
>>> since it will affect all OS's. I think it would be ok with an 'if
>>> defined(linux)' though.
>> Yes, it shut be an solution for all OS's.
>> I thing the file can put at /var/run on all Unix like OS's.
>> Or have someone other voice?
> Solaris 8 has /var/run. Good. But it's not user writable, and I do my own
> local install with everything running as me, not root, so this won't work for
> Of course, I'm still using nas 1.7 (or earlier?) because it just works. :-)
Ok, the current plan then for 1.9.1 is:
- Make MixerInit = no the default.
- use /var/run/ for linux only. The issue Ray brings up will also
be a problem for linux users that start NAS as non-root in that
/var/run is not user-writable on Linux either. The workaround
would be to start nas with '-pn' (partial network). This would
work for Solaris too, and may be what we do in the future, but I
do not want to incorporate a 'large impact' fix like this into
What say ye?
Happy cheese in fear | Jon Trulson
against oppressor, rebel! | mailto:jon at radscan.com
Brocolli, hostage. -Unknown | #include <std/disclaimer.h>
More information about the Nas