New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gbak doesn't return error code [CORE2251] #2677
Comments
Modified by: Kirill Nesterenko (nester)description: gbak doesn't return error code when used with service manager and output redirected into the non-accessible file. E.g. bat file (there is no drive Z on the target machine): If "-y z:\log.txt" part is removed - then correct errorcode 1 is retuned. => gbak doesn't return error code when used with service manager and output redirected into the non-accessible file. E.g. bat file (there is no drive Z on the target machine): If "-y z:\log.txt" part is removed - then correct errorcode 1 is returned. |
Commented by: Ivan Pisarevsky (ivan_pisarevsky) Linux, FB3.0.5, build 33100 gbak -c -user "$IBUSER" -pass $2 -v -y "$PRTPATH/$1.rpr" "$ARCPATH/$1.gbk" "$TSTPATH/$1.gdb" -SE localhost:service_mgr if no access to file $ARCPATH/$1.gbk I can see error message: gbak: ERROR:cannot open backup file /ibbackup/****.gbk if no access to file $PRTPATH/$1.rpr there is no error message! |
Modified by: @AlexPeshkoffassignee: Alexander Peshkov [ alexpeshkoff ] |
Modified by: @AlexPeshkoffstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 4.0 Beta 2 [ 10888 ] Fix Version: 3.0.6 [ 10889 ] |
Modified by: @AlexPeshkoffenvironment: Win XP => OS independent |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: Kirill Nesterenko (nester)
Votes: 6
gbak doesn't return error code when used with service manager and output redirected into the non-accessible file.
E.g. bat file (there is no drive Z on the target machine):
--
gbak.exe -t -se 192.168.0.101:service_mgr C:\db.fdb c:\db.fbk -y z:\log.txt -user SYSDBA -password masterkey
@echo %errorlevel%
--
returns exit code 0 instead of 1.
If "-y z:\log.txt" part is removed - then correct errorcode 1 is returned.
Commits: 91c99bd 5e962f0
The text was updated successfully, but these errors were encountered: