> There's also a keyboard sequence to do it for PS/2 keyboards -- I'm
> pretty sure its CTRL-ALT-D (note that is "D" as in David, not
> DELETE!) I've not tested to find out if it works for USB keyboards.
It's F1-A
___
opensolaris-code mailing list
Garrett D'Amore wrote:
> Alexandra (Sasha) Fedorova wrote:
>
>> Hello,
>>
>> When I used to debug Solaris on SPARC, I'd send a "break" signal Ctrl-] to
>> the console, the system would drop into "ok" prompt and I'd start mdb like
>> this: "mdb -k". However, on x86 platform the break signal do
Alexandra (Sasha) Fedorova wrote:
> Hello,
>
> When I used to debug Solaris on SPARC, I'd send a "break" signal Ctrl-] to
> the console, the system would drop into "ok" prompt and I'd start mdb like
> this: "mdb -k". However, on x86 platform the break signal does not drop you
> into the ok prom
Hello,
When I used to debug Solaris on SPARC, I'd send a "break" signal Ctrl-] to the
console, the system would drop into "ok" prompt and I'd start mdb like this:
"mdb -k". However, on x86 platform the break signal does not drop you into the
ok prompt, and I recall reading somewhere online tha
Mike Gerdts writes:
> A few seconds later in the global zone I did:
>
> # ps -fe | grep which | wc -l
> 3911
> # ps -fe | grep which | wc -l
> 4588
> # zoneadm -z $zone halt
Perhaps your $HOME/.cshrc has a "which" in it. If so, then that'd be
pretty toxic and would cause the explosion yo
On Fri, Jul 11, 2008 at 10:12 AM, James Carlson <[EMAIL PROTECTED]> wrote:
> Daniel Templeton writes:
>> So, correct me if I'm wrong, but shouldn't csh -f ignore the
>> $HOME/.cshrc file?
>
> It should. For what it's worth:
>
> # csh -f /usr/bin/which which
> /usr/bin/which
> # ps | grep which | w
Daniel Templeton writes:
> So, correct me if I'm wrong, but shouldn't csh -f ignore the
> $HOME/.cshrc file?
It should. For what it's worth:
# csh -f /usr/bin/which which
/usr/bin/which
# ps | grep which | wc -l
0
#
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
It used to be that which started out as:
#! /usr/bin/csh
At some later time it changed to:
#! /usr/bin/csh -f
Now I see that there is an explicit sourcing of the .cshrc, undoing
the benefit of -f.
$ grep source /usr/bin/which
if ( -r ~/.cshrc && -f ~/.cshrc ) source ~/.cshrc
which should do s
So, correct me if I'm wrong, but shouldn't csh -f ignore the
$HOME/.cshrc file? That totally explains the non--f behavior I was
seeing, though, as James also pointed out.
Thanks,
Daniel
Mike Gerdts wrote:
> On Fri, Jul 11, 2008 at 12:38 AM, Daniel Templeton
> <[EMAIL PROTECTED]> wrote:
>
>>
Daniel Templeton writes:
> As I play around with this further, I'm seeing the same pattern for pretty
> much any command I run from csh, with or without -f, e.g. "csh /usr/bin/echo
> test" or "csh -c echo test". WTF??? This is /usr/bin/csh. Clearly such a
> severe issue hasn't survived throug
hi,
i want to pull up the network card information which includes the name of
the controller name, manufacturer and the MAC address. I need to know the C
interfaces and the header files which can be used for that. It would be great
if i get to know the command which infact provides that i
11 matches
Mail list logo
