This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Hiding console when running Cygwin utility from Task Scheduler.

On 2017-08-02, Brian Inglis wrote:

> I believe that conhost, mintty, ptys, cron, and Cygwin program startup open
> handles for stdin, stdout, stderr to talk on, as those are assumed to be
> available by most programs, rather than closing anything, which could terminate
> program execution.
Small correction about `conhost`:

It is native Windows app. I believe that it is responsible to drawing native
console and I want to hide it.

> Cygwin run allows you to run a Windows GUI program with a hidden console window.
I think situation a bit different. run.exe is able to "hide" console of
console app. Cygwin compiles each app as console as GUI app have no access to
stdin/stdout and can't attach to any console, as state run(1):

      Windows programs are either GUI programs or console programs. When
      started console programs will either attach to an existing console or
      create a new one. GUI programs can never attach to an exiting console.
      There is no way to attach to an existing console but hide it if started
      as GUI program.

>> My goal to avoid any splashes on screen and possible keyboard focus stealing
>> from sudden task execution.
> I never see any windows or conhost processes running Cygwin Scheduled Tasks with
> the previous suggestions and these settings:
>>> You may also have to set the (o) Run whether user is logged on or not
>>> radio button, [X] Do not store password..., and [X] Run with highest
>>> privileges check boxes.
> where the first may be most significant in this case;

Thanks! That is. When I change from:

 [x] run only when user logged in


 [x] run whether user is logged on or not

I don't see that temporary console window.

I was going to check what happen with Cygwin app launched from nssm and see

  2017-04-26: Users of Windows 10 Creators Update should use prelease build
  2.2.4-101 to avoid an issue with services failing to start. If for some
  reason you cannot use that build you can also set AppNoConsole=1 in the
  registry, noting that applications which expect a console window may behave

So Microsoft recently changed something in its console related API...


Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]