From: Hans Deragon <hans@deragon.biz>
To: Ian Kent <raven@themaw.net>
Cc: autofs@linux.kernel.org
Subject: Re: auto.net gets a key with a path under SLES9.
Date: Tue, 15 Nov 2005 11:28:39 -0500 [thread overview]
Message-ID: <437A0CB7.20701@deragon.biz> (raw)
In-Reply-To: <Pine.LNX.4.63.0511160007560.2260@donald.themaw.net>
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 <raven@themaw.net> 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.
Best regards,
Hans Deragon
--
Consultant en informatique/Software Consultant
Deragon Informatique inc.
http://www.deragon.biz Open source (contribution):
mailto://hans@deragon.biz http://autopoweroff.deragon.biz
next prev parent reply other threads:[~2005-11-15 16:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 20:03 auto.net gets a key with a path under SLES9 Hans Deragon
2005-11-14 20:56 ` Jeff Moyer
2005-11-15 13:29 ` Ian Kent
2005-11-15 14:31 ` Jeff Moyer
2005-11-15 16:14 ` Ian Kent
2005-11-15 16:28 ` Hans Deragon [this message]
2005-11-15 16:40 ` Ian Kent
2005-11-15 17:14 ` Jeff Moyer
2005-11-17 18:23 ` Hans Deragon
2005-11-25 21:17 ` Hans Deragon
2005-11-27 13:40 ` Ian Kent
2005-11-28 17:53 ` Hans Deragon
2005-12-01 16:24 ` Ian Kent
2005-11-30 19:46 ` Hans Deragon
2005-12-01 16:20 ` Ian Kent
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=437A0CB7.20701@deragon.biz \
--to=hans@deragon.biz \
--cc=autofs@linux.kernel.org \
--cc=raven@themaw.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.