Subject | Re: [firebird-support] Re: gsec and stdout on Windows 7 |
---|---|
Author | Mark Rotteveel |
Post date | 2010-02-20T20:28:33Z |
On 1-2-2010 14:04, Mark Rotteveel wrote:
Windows 7 64 bit with Firebird 2.1.3 (64 bit).
I tested:
* With adminstrator user in cmd (not run as administrator) : File is
created just fine (in user folder due to write rights)
* With administrator user in cmd (run as administrator) : File is
created just fine (in Program Files\Firebird\Firebird_2_1 folder)
* With standard (non-administrator) user in cmd : File is created just
fine (in user folder due to write rights)
command line used:
gsec -user sysdba -password masterke -display > out.txt
--
Mark Rotteveel
>> Doesn't anyone have an idea what might be the problem? I know severalI finally got around to testing this: I am unable to reproduce this on
>> people who exactly have this problem whereas I can't reproduce it myself.
>>
>> The short version is: why does "gsec -display>out.txt" just create an
>> empty file with nothing in it?
>
> What happens with gsec -display>&2 out.txt
>
>> &2 selects the stderr (> or>&1 selects stdout)
>
> (I currently don't have a Firebird installaton handy to check this, and my Windows 7 computer is broken).
Windows 7 64 bit with Firebird 2.1.3 (64 bit).
I tested:
* With adminstrator user in cmd (not run as administrator) : File is
created just fine (in user folder due to write rights)
* With administrator user in cmd (run as administrator) : File is
created just fine (in Program Files\Firebird\Firebird_2_1 folder)
* With standard (non-administrator) user in cmd : File is created just
fine (in user folder due to write rights)
command line used:
gsec -user sysdba -password masterke -display > out.txt
--
Mark Rotteveel