> > but wasn't able to build a recent nam snapshot on Solaris to verify > that this was a planned change in behaviour. > > I simply dropped back to nam1.0a4/ns2.1b2 so that I could see what I > was doing with nam. Building a recent nam snapshot might fix the > interaction with 2.1b3. > This is a planned nam function. You can simply delete this line if you can not make nam-snapshot work thanks Ya