TT_HOST_NETFILE_FILE(3)

okay so, bestie, we're in the library call manual page for tt_host_netfile_file, and the whole vibe is mapping between canonical and local pathnames on a remote host. buckle up 💖

🌸 NAME 🌸

tt_host_netfile_file — map between canonical and local pathnames on a remote host

✨ SYNOPSIS ✨

#include &<Tt/tt_c.h>
char *tt_host_netfile_file(
const char *host,
const char *netfilename);

💅 DESCRIPTION 💅

The tt_host_netfile_file function performs a conversion equivalent to that of the tt_netfile_file(3) function, but performs it on a remote host. like, same energy, different host, yk? 🦋

The host argument is the host on which the file resides. The netfilename argument is a copy of a null-terminated string returned by tt_netfile_file(3) or tt_host_netfile_file(3). periodt.

💖 RETURN VALUE 💖

Upon successful completion, the tt_host_netfile_file function returns a freshly allocated null-terminated string of unspecified format, which can be passed to tt_host_netfile_file(3); otherwise, it returns an error pointer. The application can use tt_ptr_error(3) to extract one of the following Tt_status values from the returned pointer:

• TT_ERR_DBAVAIL — the ToolTalk database server could not be reached on host, perhaps because the host is unavailable or cannot be reached through the network. the server is giving ghosting 💀
• TT_ERR_DBEXIST — the ToolTalk database server is not properly installed on host. not installed properly? tragic.
• TT_ERR_NETFILE — the netfilename is not a valid netfilename. invalid, bestie, invalid.
• TT_ERR_UNIMP — the ToolTalk database server contacted is of a version that does not support tt_host_netfile_file. old server, no slay 😭

🧚 APPLICATION USAGE 🧚

The tt_file_netfile(3), tt_netfile_file(3), tt_host_file_netfile(3) and tt_host_netfile_file(3) functions allow an application to determine a path valid on remote hosts, perhaps for purposes of constructing a command string valid for remote execution on that host. By composing the two calls, paths for files not accessible from the current host can be constructed. For example, if path /sample/file is valid on host A, a program running on host B can use

tt_host_netfile_file("C", tt_host_file_netfile("A", "/sample/file"))

to determine a path to the same file valid on host C, if such a path is possible. cross-host path slay 🔥

Allocated strings should be freed using either tt_free(3) or tt_release(3). don't forget, bb 🫶

The tt_open(3) function need not be called before tt_host_netfile_file. no extra setup required, iconic.

🦋 SEE ALSO 🦋

• Tt/tt_c.h - Tttt_c(5)
• tt_file_netfile(3)
• tt_netfile_file(3)
• tt_host_file_netfile(3)
• tt_open(3)
• tt_free(3)
• tt_release(3)

---

that's the whole page, bestie 💅✨ — signed off from the tt_host_netfile_file library call manual page; the footer has no date or extra version info stamped on it, so we move 🌈👑