Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
L
liblongpath-rsync
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
liblongpath
liblongpath-rsync
Commits
cbce490e
Commit
cbce490e
authored
Jan 24, 2000
by
Andrew Tridgell
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
reinstated the MAX_READ_BUFFER code. Its a nasty tradeoff - using lots
of memory vs. ssh bugs. uggh.
parent
74a7f81d
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
3 additions
and
5 deletions
+3
-5
io.c
io.c
+2
-4
rsync.h
rsync.h
+1
-1
No files found.
io.c
View file @
cbce490e
...
...
@@ -255,9 +255,6 @@ static void read_check(int f)
read_buffer_p
=
read_buffer
;
}
if
(
n
>
MAX_READ_BUFFER
/
4
)
n
=
MAX_READ_BUFFER
/
4
;
if
(
read_buffer_p
!=
read_buffer
)
{
memmove
(
read_buffer
,
read_buffer_p
,
read_buffer_len
);
read_buffer_p
=
read_buffer
;
...
...
@@ -385,7 +382,8 @@ static void writefd_unbuffered(int fd,char *buf,int len)
fd_count
=
fd
;
if
(
!
no_flush_read
)
{
reading
=
(
buffer_f_in
!=
-
1
);
reading
=
(
buffer_f_in
!=
-
1
)
&&
(
read_buffer_len
<
MAX_READ_BUFFER
);
}
if
(
reading
)
{
...
...
rsync.h
View file @
cbce490e
...
...
@@ -58,7 +58,7 @@
#define CHUNK_SIZE (32*1024)
#define MAX_MAP_SIZE (256*1024)
#define IO_BUFFER_SIZE (4092)
#define MAX_READ_BUFFER (1024*1024)
#define MAX_READ_BUFFER (10
*10
24*1024)
#define MAX_ARGS 1000
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment