Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Tue, 7 Aug 2001 11:41:53 -0400 (EDT)
From: Prentis Brooks <prentis AT aol DOT net>
To: <cygwin AT cygwin DOT com>
Subject: strange ps behavior
Message-ID: <Pine.GSO.4.33.0108071135060.3206-100000@magetower.office.aol.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Ok, I have 2 systems that are very similar in setup.  However, one is a
PDC and the other is a member server.

The strangeness is that a ps -efW does not give the same output on both.
On the PDC I get the expected output, but not on any member server.
On both servers I am logged into the host via sshd under cygrunsrv as the
local root account (on the PDC this of course means I am the Domain root).

Note: root = Administrator

It appears that the member servers are ignoring the -W option since all I get
is the cygwin processes.

$CYGWIN = "binmode tty ntsec"

Didn't want to spew a full cygcheck output here unless needed, so if anyone
has an idea, let me know.  If you need more info, let me know and I will
provide it.

Prentis Brooks	| prentis AT aol DOT net | 703-265-0914 | AIM: PrentisB
System Administrator - Web Infrastructure & Security

       A knight is sworn to valor.  His heart knows only virtue.  His blade
       defends the helpless.  His word speaks only truth.  His wrath undoes the
       wicked. - the old code of Bowen, last of the dragonslayers


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/