public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* "CYGWIN=wincmdln" does not give me nuts
@ 2014-09-22 17:11 Пётр Б.
  2014-09-23 12:31 ` Christian Franke
       [not found] ` <331276296.20140923004634@mtu-net.ru>
  0 siblings, 2 replies; 5+ messages in thread
From: Пётр Б. @ 2014-09-22 17:11 UTC (permalink / raw)
  To: cygwin

I was frustrated by not being able to view CMD of Cygwin processes in
Windows tools. After a bit of research I found the talk about the
wincmdln option and saw it mentioned in changelog.

However, setting it did not take any effect even after reboot,

Windows 7 SP1 Prof x64, Cygwin 1.7.32.0274 x86_64.

Am I doing it wrong?

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: "CYGWIN=wincmdln" does not give me nuts
       [not found] ` <331276296.20140923004634@mtu-net.ru>
@ 2014-09-23  8:53   ` Пётр Б.
  2014-09-26 12:59     ` Пётр Б.
  2014-10-19 17:42   ` Пётр Б.
  1 sibling, 1 reply; 5+ messages in thread
From: Пётр Б. @ 2014-09-23  8:53 UTC (permalink / raw)
  To: cygwin

>I hope you aren't using 32-bit tools to view environemnt of 64-bit
applications, do you?

I am not. I see the argv[0] in ProcExp64 - executable name - and nothing more.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: "CYGWIN=wincmdln" does not give me nuts
  2014-09-22 17:11 "CYGWIN=wincmdln" does not give me nuts Пётр Б.
@ 2014-09-23 12:31 ` Christian Franke
       [not found] ` <331276296.20140923004634@mtu-net.ru>
  1 sibling, 0 replies; 5+ messages in thread
From: Christian Franke @ 2014-09-23 12:31 UTC (permalink / raw)
  To: cygwin

Пётр Б. wrote:
> I was frustrated by not being able to view CMD of Cygwin processes in
> Windows tools. After a bit of research I found the talk about the
> wincmdln option and saw it mentioned in changelog.
>
> However, setting it did not take any effect even after reboot,
>
> Windows 7 SP1 Prof x64, Cygwin 1.7.32.0274 x86_64.

Could not reproduce.

Testcase:

$ uname -srvm
CYGWIN_NT-6.1 1.7.32(0.274/5/3) 2014-08-13 23:06 x86_64

$ export CYGWIN=wincmdln

$ bash -c "bash -c 'echo \$CYGWIN; sleep 1000'"
wincmdln

Command lines of 'inner' bash and sleep are visible in Task-Manager, 
Process Explorer and Process Hacker 2.

Christian


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: "CYGWIN=wincmdln" does not give me nuts
  2014-09-23  8:53   ` Пётр Б.
@ 2014-09-26 12:59     ` Пётр Б.
  0 siblings, 0 replies; 5+ messages in thread
From: Пётр Б. @ 2014-09-26 12:59 UTC (permalink / raw)
  To: cygwin

I can give more information but I just do not know what else to say.
Everything else except CYGWIN variable is unchanged since
installation.

2014-09-23 10:52 GMT+04:00, Пётр Б. <satnatantas@gmail.com>:
>>I hope you aren't using 32-bit tools to view environemnt of 64-bit
> applications, do you?
>
> I am not. I see the argv[0] in ProcExp64 - executable name - and nothing
> more.
>

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: "CYGWIN=wincmdln" does not give me nuts
       [not found] ` <331276296.20140923004634@mtu-net.ru>
  2014-09-23  8:53   ` Пётр Б.
@ 2014-10-19 17:42   ` Пётр Б.
  1 sibling, 0 replies; 5+ messages in thread
From: Пётр Б. @ 2014-10-19 17:42 UTC (permalink / raw)
  To: cygwin

However, after assuming that developers are smarter than I am, i found it.

In XP I would have zero problems, but I was using Seven! I created a
per-user variable "CYGWIN" thinking that it will be visible to all
programs.

But operating system thinks otherwise - per-user variables only affect
programs launched under his account.

Programs with elevated priveleges happen to not count because they are
launched with "SYSTEM" account.

You should have asked me about whether "CYGWIN" is visible in the
output of "set" command - it wasn't.


Making CYGWIN a system variable worked as it should.


2014-09-23 0:46 GMT+04:00, Andrey Repin <anrdaemon@yandex.ru>:
> Greetings, Пётр Б.!
>
>> I was frustrated by not being able to view CMD of Cygwin processes in
>> Windows tools. After a bit of research I found the talk about the
>> wincmdln option and saw it mentioned in changelog.
>
>> However, setting it did not take any effect even after reboot,
>
>> Windows 7 SP1 Prof x64, Cygwin 1.7.32.0274 x86_64.
>
>> Am I doing it wrong?
>
> I hope you aren't using 32-bit tools to view environemnt of 64-bit
> applications, do you?
>
> CYGWIN=nodosfilewarning wincmdln winsymlinks:nativestrict
>
>> From Far x86:
>
> Module:                bash.exe
> PID:                   5168
> Parent PID:            7468
> Priority:              8
> Threads:               6
> Owner:                 daemon2\anrdaemon
> (S-1-5-21-2916456319-725650362-4229827469-1000)
> Session:               1
>
> Started at:            00:42:16
> Uptime:                00:00:51
>
>
> GDI Objects:           4
> USER Objects:          1
>
> Processor Time:          00:00:00.000       0%
> Privileged Time:         00:00:00.000       0%
> User Time:               00:00:00.000       0%
> Handle Count:                   131
> Page File Bytes:            6852608
> Page File Bytes Peak:       6856704
> Working Set:                5939200
> Working Set Peak:           5939200
> Pool Nonpaged Bytes:           8824
> Pool Paged Bytes:             99792
> Private Bytes:              6852608
> Page Faults:                   1464      0/sec
> Virtual Bytes:            599552000
> Virtual Bytes Peak:       599552000
> IO Data Bytes:                 6398      0/sec
> IO Read Bytes:                 6313      0/sec
> IO Write Bytes:                  85      0/sec
> IO Other Bytes:                4328      0/sec
> IO Data Operations:               9      0/sec
> IO Read Operations:               6      0/sec
> IO Write Operations:              3      0/sec
> IO Other Operations:            237      0/sec
>
> Modules:
>   Base      Size    Path, version, description
>   75761282  2C5B30
>
>
>> From Far x86_64:
>
> Module:                bash.exe
> Full path:             C:\Programs\Cygwin_64\bin\bash.exe
> PID:                   5168
> Parent PID:            7468
> Priority:              8
> Threads:               6
> Owner:                 daemon2\anrdaemon
> (S-1-5-21-2916456319-725650362-4229827469-1000)
> Session:               1
>
> Started at:            00:42:16
> Uptime:                00:01:31
>
> Command Line:
> C:\Programs\Cygwin_64\bin\bash.exe
>
> Current Directory:     D:\PlugRing\Utils\
>
> Environment:
>
> PATH=C:\Programs\Cygwin_64\bin;C:\Program Files (x86)\NVIDIA
> Corporation\PhysX\Common;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program
> Files\WinRAR;C:\Program
> Files\7-Zip;C:\DrWeb;C:\Programs\Subversion\bin;C:\Users\anrdaemon\bin;C:\usr\util;C:\usr\ARH;C:\USR\BP7\BIN;C:\usr\FPC-2.4.2\bin\i386-Win32;C:\Programs\CVSNT\
> SYSTEMDRIVE=C:
> SYSTEMROOT=C:\Windows
> WINDIR=C:\Windows
>
> GDI Objects:           4
> USER Objects:          1
>
> Processor Time:          00:00:00.000       0%
> Privileged Time:         00:00:00.000       0%
> User Time:               00:00:00.000       0%
> Handle Count:                   131
> Page File Bytes:            6852608
> Page File Bytes Peak:       6856704
> Working Set:                5939200
> Working Set Peak:           5939200
> Pool Nonpaged Bytes:           8824
> Pool Paged Bytes:             99792
> Private Bytes:              6852608
> Page Faults:                   1464      0/sec
> Virtual Bytes:            599552000
> Virtual Bytes Peak:       599552000
> IO Data Bytes:                 6398      0/sec
> IO Read Bytes:                 6313      0/sec
> IO Write Bytes:                  85      0/sec
> IO Other Bytes:                4328      0/sec
> IO Data Operations:               9      0/sec
> IO Read Operations:               6      0/sec
> IO Write Operations:              3      0/sec
> IO Other Operations:            237      0/sec
>
> Modules:
>   Base      Size    Path, version, description
>   0000000100400000   A8000 C:\Programs\Cygwin_64\bin\bash.exe
> ...cut...
>
> Handles:
> Handle  Access   Type         Name
>     4  00000009
>     8  00000003
> ...cut...
>
>
> --
> WBR,
> Andrey Repin (anrdaemon@yandex.ru) 23.09.2014, <0:41>
>
> Sorry for my terrible english...

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2014-10-19 17:42 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-09-22 17:11 "CYGWIN=wincmdln" does not give me nuts Пётр Б.
2014-09-23 12:31 ` Christian Franke
     [not found] ` <331276296.20140923004634@mtu-net.ru>
2014-09-23  8:53   ` Пётр Б.
2014-09-26 12:59     ` Пётр Б.
2014-10-19 17:42   ` Пётр Б.

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).