All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas <nicolas.delaby@ezeep.com>
To: util-linux@vger.kernel.org
Subject: nsenter: passing command arguments
Date: Thu, 17 Apr 2014 10:34:05 +0200	[thread overview]
Message-ID: <534F91FD.4020803@ezeep.com> (raw)

Hi,
I'm struggling with nsenter to call commands with options because they 
are caught by nsenter and complain this is an invalid option.

How can I pass any arbitrary argument ?

Thanks for reading,
Nicolas

```
$ nsenter --target $PID --mount --uts --ipc --net --pid ls -a
nsenter: invalid option -- 'a'

Usage:
  nsenter [options] <program> [args...]

Options:
  -t, --target <pid>     target process to get namespaces from
  -m, --mount [=<file>]  enter mount namespace
  -u, --uts   [=<file>]  enter UTS namespace (hostname etc)
  -i, --ipc   [=<file>]  enter System V IPC namespace
  -n, --net   [=<file>]  enter network namespace
  -p, --pid   [=<file>]  enter pid namespace
  -U, --user  [=<file>]  enter user namespace
  -S, --setuid <uid>     set uid in user namespace
  -G, --setgid <gid>     set gid in user namespace
  -r, --root  [=<dir>]   set the root directory
  -w, --wd    [=<dir>]   set the working directory
  -F, --no-fork          do not fork before exec'ing <program>

  -h, --help     display this help and exit
  -V, --version  output version information and exit

For more details see nsenter(1).

```

-- 

Nicolas Delaby · Software Engineer · ezeep.com

ezeep GmbH · Ohlauer Str. 43 · 10999 Berlin · Germany

Registry Court: Charlottenburg · HRB133318 · Managing partner: Sascha 
Kellert

             reply	other threads:[~2014-04-17  8:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-17  8:34 Nicolas [this message]
2014-04-17 22:17 ` nsenter: passing command arguments Bernhard Voelker
2014-04-18 11:12   ` Karel Zak
2014-04-22  7:56   ` Nicolas

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=534F91FD.4020803@ezeep.com \
    --to=nicolas.delaby@ezeep.com \
    --cc=util-linux@vger.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.