Provide ability to specify extra-long name of log when doing gbak to avoid
"attempt to store 256 bytes in a clumplet" message
-----------------------------------------------------------------------------------------------------------------------------
Key: CORE-4398
URL: http://tracker.firebirdsql.org/browse/CORE-4398
Project: Firebird Core
Issue Type: Improvement
Components: GBAK
Reporter: Pavel Zotov
Priority: Minor
Currently the following command:
/opt/fb25/bin/gbak -se localhost/3253:service_mgr -v -y
/var/db/fb25/A012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890.log
-b /var/db/fb25/tmp25.fdb /var/db/fb25/tmp25.fbk
- shows:
gbak: ERROR:Internal error when using clumplet API: attempt to store 256 bytes
in a clumplet with maximum size 255 bytes
gbak:Exiting before completion due to errors
It is rarely need to specify such long name of log, may be it can occur if we
have too deep folders tree with long names of each sub-folder.
But anyway it will be useful to increase current limit.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
