[
https://issues.apache.org/jira/browse/GUACAMOLE-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889703#comment-17889703
]
Nick Couchman commented on GUACAMOLE-1112:
------------------------------------------
Would using this define/marco resolve this issue?
{code}
_FILE_OFFSET_BITS
Defining this macro with the value 64 automatically converts
references to 32-bit functions and data types related to file I/O and
filesystem operations into references to
their 64-bit counterparts. This is useful for performing
I/O on large files (> 2 Gigabytes) on 32-bit systems. It is also useful
when calling functions like
copy_file_range(2) that were added more recently and that come
only in 64-bit flavors. (Defining this macro permits correctly written
programs to use large files with
only a recompilation being required.)
64-bit systems naturally permit file sizes greater than 2
Gigabytes, and on those systems this macro has no effect.
{code}
> RDPDR file read/write may be truncated depending on platform
> ------------------------------------------------------------
>
> Key: GUACAMOLE-1112
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1112
> Project: Guacamole
> Issue Type: Bug
> Components: RDP
> Reporter: Mike Jumper
> Priority: Minor
>
> While the issue with 32-bit read/write operations has been largely addressed
> by GUACAMOLE-764, these read/write operations still rely on {{lseek()}},
> which is not required to implement 64-bit seeks ({{off_t}} is not guaranteed
> to be 64-bit). Additional changes are likely needed to ensure that seeking
> within files works with 64-bit offsets in a cross-platform way.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
