From: Craig B. <cba...@us...> - 2006-03-14 05:59:58
|
"Justin Best" writes: > Thanks for your help, Craig! I appreciate it so very much. >=20 > I've filed a bug report with Samba, as you suggested. > https://bugzilla.samba.org/show_bug.cgi?id=3D3592=20 >=20 > Out of curiosity, though, it seems that you still have an open bug that= > references the same problem. In bug 563 > https://bugzilla.samba.org/show_bug.cgi?id=3D563 > you mentioned "smbclient tar extract still only writes a maximum 2GB fi= le; > not sure why." Am I right in assuming that this is the same issue? =20 That's a bug in the other direction (restoring large files). Your bug is padding large locked files when creating an archive). > In any event, I'm still unfamiliar with how I should go about fixing th= is in > my case. I assume that I need to download the source and modify it and > recompile smbclient... but I haven't a clue on how to "make padsize an > unsigned int", as you suggest. I'm afraid that I know some ASP and PHP,= and > that's about it. Any direction about where to start with this would be > appreciated. You should download the latest source for samba, and edit samba-3.X.X/source/client/clitar.c so that this line: static int padit(char *buf, int bufsize, int padsize) instead reads: static int padit(char *buf, int bufsize, SMB_BIG_UINT padsize) Then you should be able to run configure and make, then use the resulting smbclient executable. I haven't tested this fix, but it should be correct.=20 Craig |