The man page for screen says that I can create a detatched screen
running with a set command in it by doing this:
$ screen -dm $command
However, it doesn't work. Screen exits without creating the detached
screen.
If I say
$ screen $command
...I get dropped into a screen session running $command as I would
expect.
What's the magic invocation I'm missing?
Also, the next step will be for root to launch said screen session as
someone else during boot time; am I asking for trouble by trying it?
# su - user -c screen -dmS $Label $command
Thanks for any insights or pointers to web resources I can use to
learn from.
--
/\oo/\
/ /()\ \ David Mackintosh |
dave at xdroop.com | http://www.xdroop.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL:
<http://lists.centos.org/pipermail/centos/attachments/20080722/d6ebfa77/attachment-0001.sig>
On Tue, Jul 22, 2008 at 01:02:07PM -0400, David Mackintosh wrote:> The man page for screen says that I can create a detatched screen > running with a set command in it by doing this: > > $ screen -dm $command > > However, it doesn't work. Screen exits without creating the detached > screen.screen -dm isn't the same as screen -d -m. Try the latter. -- lfr 0/0 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: <http://lists.centos.org/pipermail/centos/attachments/20080722/5892ecad/attachment-0001.sig>
On Tue, 2008-07-22 at 18:07 +0100, Luciano Rocha wrote:> On Tue, Jul 22, 2008 at 01:02:07PM -0400, David Mackintosh wrote: > > The man page for screen says that I can create a detatched screen > > running with a set command in it by doing this: > > > > $ screen -dm $command > > > > However, it doesn't work. Screen exits without creating the detached > > screen. > > screen -dm isn't the same as screen -d -m. Try the latter.Just an FYI... You *may* be right, however... "Standards" dictate that "flags" can be combined into a single parameter. This is "eased" (debatable IMO) by the "getopts" function in bash, getopt(1) command and getopt(3) function call for C et al. Unfortunately, *some* few programs do not implement this correctly. But over the years, as programs have been "cleaned up" and replaced, their number has (thankfully) diminished.> <snip sig stuff>I note the OP has solved it. -- Bill