Yes, a verbose flag would be great. Greetings.
Walter. On Tue, Nov 12, 2013 at 7:26 AM, Tim Ward <[email protected]> wrote: > > > Depends whether you're used to Unix commands, which typically say nothing > when they've done what they think you meant (thus not giving you a clue > whether what they did was what you actually wanted or not), or commands on > pretty well all other systems which are more likely to confirm what it is > they've actually done (so that you can see whether or not it was what you > wanted). > > One would, however, expect a command which followed the Unix convention > (to say nothing at all on success) to have a "verbose" flag which did cause > a suitable success message to be produced. > > > On 12/11/2013 11:20, W O wrote: > > > Me too, and for sure many other people too. > > Greetings. > > Walter. > > > > On Tue, Nov 12, 2013 at 1:05 AM, <[email protected]> wrote: > >> >> >> I see.... >> >> >> I would expect to see message that everything is ok...or something like >> that... >> >> >> ---In [email protected], >> <sistemas2000profesional@...><sistemas2000profesional@...>wrote: >> >> That's a problem with GFIX. If everything is ok then it says .... >> nothing. >> >> Greetings. >> >> Walter. >> >> >> >> On Fri, Nov 8, 2013 at 5:22 AM, <brucedickinson@...> wrote: >> >> >> >> Hi guys, >> >> I have this strange problem which I do not get it. I am trying to check >> my database with given options: >> >> gfix -user SYSDBA -password masterkey -v MYBASE.FDB >> >> and.. nothing, no return info. Nothing. >> >> When I intentionally give non existant file, like this: >> >> gfix -user SYSDBA -password masterkey -v blabla.FDB >> >> then I am getting info about error. >> >> What am I doing wrong? >> >> Regards. >> >> >> > > > -- > Tim Ward > > >
