libssh2_sftp_fsync(3)

✨ libssh2_sftp_fsync ✨

okay bestie, we're diving into the libssh2 manual, page libssh2_sftp_fsync(3) 💅 this one's short and sweet and honestly iconic.

🦋 NAME 🦋

libssh2_sftp_fsync — make that remote file actually hit the disk, no cap

🌸 SYNOPSIS 🌸

#include <libssh2.h>
#include <libssh2_sftp.h>

int
libssh2_sftp_fsync(LIBSSH2_SFTP_HANDLE *handle)

💖 DESCRIPTION 💖

so basically this function makes the remote server sync the file's data and metadata to disk. literally the remote equivalent of fsync(2), periodt. 💾✨

for this to work you need fsync@openssh.com support on the server. no server support = no fsync, sorry bestie 😭

• handle — the SFTP File Handle, as returned by libssh2_sftp_open_ex(3). that's your golden ticket 🎀

👑 RETURN VALUE 👑

returns 0 on success, or a negative number on failure. 💀

if you're running in non-blocking mode, it returns LIBSSH2_ERROR_EAGAIN when it would otherwise block. and like… yes, LIBSSH2_ERROR_EAGAIN is technically a negative number, but it is not really a failure per se. it's giving "hold on, try again later" energy, not "everything is broken" energy. 🙈

🔥 ERRORS 🔥

• LIBSSH2_ERROR_ALLOC — an internal memory allocation call failed. the malloc said no 😭
• LIBSSH2_ERROR_SOCKET_SEND — couldn't send data on the socket. the socket is not socketing 💀
• LIBSSH2_ERROR_SFTP_PROTOCOL — an invalid SFTP protocol response came back on the socket, or an SFTP operation made the server return an errorcode. specifically, this one can pop up if the SSH server doesn't support the fsync operation — in that case the SFTP subcode LIBSSH2_FX_OP_UNSUPPORTED gets returned. so if you see that, it's the server, not you 🫶

🌈 AVAILABILITY 🌈

added in libssh2 1.4.4 and OpenSSH 6.3. vintage, but make it fashion ⭐

🧚 SEE ALSO 🧚

• fsync(2)

and that's the whole vibe, bestie! go forth and fsync responsibly 💅

this page came to you from the libssh2 manual, dated 8 Apr 2013 — mwah, xoxo, sync your disks 💖