No admin setup questions

[Lavrentiev, Anton (NIH/NLM/NCBI) [C]]

> Your non-elevated non-admin USER may not have perms to create logs in any of the 
> usual places /var/log/, /tmp/, ./, /

No, I'm the sole user of this installation (that is, all files are "owned" by my user ID, under the Cygwin root)...

The real reason was explained to me in a private response that I am posting below.

Thanks for prepping the procmail postinstall patch -- hopefully, it'll be seen by the package maintainer and adopted into the package, appropriately.

Thanks,
Anton Lavrentiev

-----Original Message-----
From: Adam Dinwoodie <adam@dinwoodie.org> 
Sent: Tuesday, February 23, 2021 2:17 PM
To: Lavrentiev, Anton (NIH/NLM/NCBI) [C] <lavr@ncbi.nlm.nih.gov>
Subject: Re: No admin setup questions

On Tue, 23 Feb 2021 at 16:08, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:
> Also, I see a lot of messages in the cmd.exe "terminal" window, from where setup was run:  it seems to be logging all actions, including that I was not allowed to open service controller, and missing some rights, what the download and install path are, which packages are being downloaded, extracted and installing.
>
> I do not remember seeing any of those in a "more regular" use (without the -B, when I just click the icon with the program).
>
> Is that some sort of a debugging output left behind?  Just curios, if that's a debug version of the setup ended up on being offered for download inadvertently.

This is expected: the installer will output status to any console that
exists. If you run from a non-administrator cmd/pwsh session and
require Perimeta to escalate privileges, that breaks the link between
the console and the executable, so it can't provide that output. But
if you run from an already-elevated console, or without requiring
admin privileges in the first place, the installer will print details
of its status to the console.