==> Regarding Re: [autofs] auto.net gets a key with a path under SLES9.; Ian Kent <[EMAIL PROTECTED]> adds:
raven> On Tue, 15 Nov 2005, Hans Deragon wrote: >> Ian Kent wrote: > On Tue, 15 Nov 2005, Jeff Moyer wrote: >> > >> > >> > > ==> Regarding Re: [autofs] auto.net gets a key with a path under >> SLES9.; > > Ian Kent <[EMAIL PROTECTED]> adds: >> > > >> > > raven> On Mon, 14 Nov 2005, Hans Deragon wrote: Thanks for reporting >> this > > raven> Hans. >> > > >> > > >> > > > > Greetings. >> > > > > >> > > > > >> > > > > I compiled autofs 4.1.4 for SuSE Linux Enterprise Server 9 >> (SLES9). I > > > > did found a little problem with auto.net. The >> original code has: >> > > > > >> > > > > key=$1 >> > > > > >> > > > > However, under SLES9, in my network environment, $key can be of >> the > > > > form > > > > "server/something[/otherthing]*", which is >> wrong. $key should only be > > > > a > > > > server name. I fixed the >> problem with: >> > > > > >> > > > > key=`echo $1 | perl -wp -e 's%^(\w+)(\/?.+)*$%$1%;'` >> > > > > >> > > > > My fix removes any path after the server name. >> > > >> > > raven> Interesting. I'm not sure why that's happening either. >> > > >> > > >> > > > > Exactly why automount passes a server name containg some path is >> > > > > unclear > > > > for me. But I wanted to report this here. If >> other suffer from this, > > > > you might want to consider some fix like >> mine (maybe using sed which > > > > is > > > > more standard). >> > > >> > > raven> Yep. Sounds like a good idea. >> > > >> > > raven> I'll put it on the queue of stuff for 4.1 so I can do it when >> I > > raven> eventually get back to it. >> > > >> > > Ian, this sounds more like papering over the real problem to me. Do >> you > > agree? I'd like to see some debug output. >> > >> > >> > Yep. Absolutely right. >> > >> > Your post was clearly more useful than what I had to say. >> > >> > And I agree it is likely one of the issues we have recently >> investigated. > Perhaps the SuSE folks haven't merged some of the >> recent kernel patches. >> > >> > Hans, could you spend a bit of time to get us a debug log please. >> > >> > Ian >> >> No problem. Just give me instructions on how to proceed. I am not that >> familiar with autofs and its code/features. >> raven> It is fairly straight forward. Just add --debug or just -d to the raven> master map entry for the autofs mount point you want to collect raven> debug info. for. raven> If you concerned feel free to replace host names or IP addresses (if raven> any) but please keep the trace in tact otherwise. raven> eg. raven> /net /etc/auto.net --debug raven> Should do the trick. And, as I mentioned earlier in this thread, you can find more detailed instructions on my people page, http://people.redhat.com/jmoyer/. Most notably, it also contains the steps necessary to make the syslog daemon actually capture the debug logs. -Jeff _______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
