All of lore.kernel.org
 help / color / mirror / Atom feed
From: michael@cadilhac.name (Michaël Cadilhac)
To: autofs@linux.kernel.org
Subject: Autofs screwed by getopt?
Date: Mon, 23 Jul 2007 15:34:14 +0200	[thread overview]
Message-ID: <87vecbxmzt.fsf@lrde.org> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2439 bytes --]

Hi guys!

I have a NIS based automount configuration that reads like that :

lri4-154 linux # ypcat -k auto.master
/special auto.special  -rw,intr,soft
/servers auto.servers  -rw,intr,soft
/local auto.local    -rw,intr,soft
/u auto.u            -rw,intr,soft,nosuid
/tmpsim auto.tmpsim     -rw,intr,soft
/users auto.users    -rw,intr,hard,nosuid,tcp,nfsvers=3,timeo=600,retrans=2

Didn't seem like a badly formatted one. So I launched autofs, and here's
what it said :

 * Starting automounter ...
 /special/usr/sbin/automount: option -t requires a numeric argument, got r,soft
 * Failure on /special
 /servers/usr/sbin/automount: option -t requires a numeric argument, got r,soft
 * Failure on /servers
 /local/usr/sbin/automount: option -t requires a numeric argument, got r,soft
 * Failure on /local
 /u/usr/sbin/automount: option -t requires a numeric argument, got r,soft,nosuid
 * Failure on /u
 /tmpsim/usr/sbin/automount: option -t requires a numeric argument, got r,soft
 * Failure on /tmpsim
 /users/usr/sbin/automount: option -t requires a numeric argument, got r,hard,nosuid,tcp,nfsvers=3,timeo=600,retrans=2
 * Failure on /users

Point is that the `-rw,int' is interpreted by the getopt like a bunch of
not understood options then a `t', as in `timeout'. So the next part,
e.g. `r,soft', is considered as the argument of `timeout' which is not
quite good.

What I did is that I removed the short opts for getopt in the init.d
script, but I'm not quite sure it's The Right Thing to Do.

Maybe the config got from nis is faulty, if so, just tell me, I'll
despise my sysadmin.

Thanks!

PS: In fact, it seems that the mount options are not applied at
all. Don't have a clue why.

------------------------------------------------------------------------
lri4-154 linux # automount --version
Linux automount version 4.1.3
lri4-154 linux # uname -a
Linux lri4-154 2.6.22-gentoo-r1 #1 SMP Thu Jul 19 16:20:19 CEST 2007
i686 Intel(R) Pentium(R) 4 CPU 2.80GHz GenuineIntel GNU/Linux
------------------------------------------------------------------------

-- 
 |   Michaël `Micha' Cadilhac       |    Un paradoxe autoréférent ?          |
 |   http://michael.cadilhac.name   |                                        |
 |   JID/MSN:                       |       ... Je dis pas non !             |
 `----  michael.cadilhac@gmail.com  |                                   -  --'

[-- Attachment #1.2: Type: application/pgp-signature, Size: 188 bytes --]

[-- Attachment #2: Type: text/plain, Size: 140 bytes --]

_______________________________________________
autofs mailing list
autofs@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/autofs

             reply	other threads:[~2007-07-23 13:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-23 13:34 Michaël Cadilhac [this message]
2007-07-23 14:08 ` Autofs screwed by getopt? Jeff Moyer
2007-07-23 14:21   ` Michaël Cadilhac
     [not found]     ` <x49ejizqjgj.fsf@segfault.boston.devel.redhat.com>
2007-07-23 15:07       ` Michaël Cadilhac
2007-07-23 15:19 ` Jeff Moyer
2007-07-23 16:27   ` Michaël Cadilhac

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=87vecbxmzt.fsf@lrde.org \
    --to=michael@cadilhac.name \
    --cc=autofs@linux.kernel.org \
    /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.