From: Mike Shaver <shaver@neon.ingenia.ca>
To: linux@cthulhu.engr.sgi.com (Linux/SGI list)
Subject: par and us*
Date: Fri, 8 Aug 1997 11:19:35 -0400 (EDT) [thread overview]
Message-ID: <199708081519.LAA06545@neon.ingenia.ca> (raw)
I've got a simple lock-contention program that I'm using to see how
the usema stuff works.
When I try to run the program under par, though, it only lets me trace
one of the invocations:
1 [shaver@linus ~/work/usema]$ par -s -SS -l -o lock-p.par ./lock p
1 Creating new lock.
1 Storing lock.
1 Getting lock.
1 Waiting...
(now I start the second one)
2 [shaver@linus ~/work/usema]$ par -s -SS -l -o lock-c2.par ./lock c
2 Cannot syscall trace pid 23779:Resource busy
2 Finding existing lock.
2 Getting lock.
2 [shaver@linus ~/work/usema]$
(back to the shell!)
(release the lock on the first invocation)
1
1 Releasing lock.
1 Exiting
1 [shaver@linus ~/work/usema]$
(and now I get more output from the second invocation)
2 [shaver@linus ~/work/usema]$ Waiting...
2 Releasing lock.
2 Exiting
Under normal circumstances (no par), I have to press enter on the
second one as well for it to release the lock and exit. When par is
doing its (arguably weird, maybe broken) thing, I don't have to do
that...
Is this a known problem?
Mike
--
#> Mike Shaver (shaver@ingenia.com) Ingenia Communications Corporation
#> Linux: because every cycle counts.
#>
#> "I don't know what you do for a living[...]" -- perry@piermont.com
#> "I change the world." -- davem@caip.rutgers.edu
WARNING: multiple messages have this Message-ID (diff)
From: Mike Shaver <shaver@neon.ingenia.ca>
To: Linux/SGI list <linux@cthulhu.engr.sgi.com>
Subject: par and us*
Date: Fri, 8 Aug 1997 11:19:35 -0400 (EDT) [thread overview]
Message-ID: <199708081519.LAA06545@neon.ingenia.ca> (raw)
Message-ID: <19970808151935.RY8xixSOshFejCOEbAOeMyLbS9eBwYKwCyDXt7txIqw@z> (raw)
I've got a simple lock-contention program that I'm using to see how
the usema stuff works.
When I try to run the program under par, though, it only lets me trace
one of the invocations:
1 [shaver@linus ~/work/usema]$ par -s -SS -l -o lock-p.par ./lock p
1 Creating new lock.
1 Storing lock.
1 Getting lock.
1 Waiting...
(now I start the second one)
2 [shaver@linus ~/work/usema]$ par -s -SS -l -o lock-c2.par ./lock c
2 Cannot syscall trace pid 23779:Resource busy
2 Finding existing lock.
2 Getting lock.
2 [shaver@linus ~/work/usema]$
(back to the shell!)
(release the lock on the first invocation)
1
1 Releasing lock.
1 Exiting
1 [shaver@linus ~/work/usema]$
(and now I get more output from the second invocation)
2 [shaver@linus ~/work/usema]$ Waiting...
2 Releasing lock.
2 Exiting
Under normal circumstances (no par), I have to press enter on the
second one as well for it to release the lock and exit. When par is
doing its (arguably weird, maybe broken) thing, I don't have to do
that...
Is this a known problem?
Mike
--
#> Mike Shaver (shaver@ingenia.com) Ingenia Communications Corporation
#> Linux: because every cycle counts.
#>
#> "I don't know what you do for a living[...]" -- perry@piermont.com
#> "I change the world." -- davem@caip.rutgers.edu
next reply other threads:[~1997-08-08 15:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-08 15:19 Mike Shaver [this message]
1997-08-08 15:19 ` par and us* Mike Shaver
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=199708081519.LAA06545@neon.ingenia.ca \
--to=shaver@neon.ingenia.ca \
--cc=linux@cthulhu.engr.sgi.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox