Subject | Re: Fix GBAK bug about filenames with spaces, when using ServiceManager? |
---|---|
Author | Dan Cooperstock |
Post date | 2007-12-19T14:37:45Z |
--- In firebird-support@yahoogroups.com, "Martijn Tonies"
<m.tonies@...> wrote:
call the ServiceManager directly, it's fine. But if you do it from
GBAK, you get error messages, like:
My Command:
gbak -b -se localhost:service_mgr -user sysdba -pas mypwd
-y "C:\program files\donation2\backup.log"
"C:\Program Files\Donation2\data\donation4.db"
"c:\Program Files\donation\backup\donation4.db.gbk"
Output:
gbak: ERROR:I/O error for file "files\donation2\backup.log"
gbak: ERROR: Error while trying to open file
gbak: ERROR: The system cannot find the path specified.
gbak:Exiting before completion due to errors
All of the posts end up recommending that we use Service Manager
instead. And there seems to have been at least a related bug filed
about this in the Jira in 2004, but nothing done about it.
<m.tonies@...> wrote:
>you use
> Hello Dan,
>
> > It seems this bug (it can't handle filenames with spaces, when
> > the ServiceManager) has been hanging around for a long time. Hasanyone
> > tried to fix it? It seems to me it ought not to be too hard.There are quite a few posts about this. If you use your own code and
>
> Are you sure?
>
> I'm using the Services API with filenames including spaces and it
> appears to work just fine.
>
> Martijn Tonies
call the ServiceManager directly, it's fine. But if you do it from
GBAK, you get error messages, like:
My Command:
gbak -b -se localhost:service_mgr -user sysdba -pas mypwd
-y "C:\program files\donation2\backup.log"
"C:\Program Files\Donation2\data\donation4.db"
"c:\Program Files\donation\backup\donation4.db.gbk"
Output:
gbak: ERROR:I/O error for file "files\donation2\backup.log"
gbak: ERROR: Error while trying to open file
gbak: ERROR: The system cannot find the path specified.
gbak:Exiting before completion due to errors
All of the posts end up recommending that we use Service Manager
instead. And there seems to have been at least a related bug filed
about this in the Jira in 2004, but nothing done about it.