I have a quick question with UUCP. I know how to do this with NNCP,
which is a more modern take on UUCP, but I was wondering whether this
workflow is possible with UUCP, using TCP connections.

I have machine B, which is on all the time. Machine A wants to send a
file to machine C, where machine C may not be on the network (its
powered down). Ideally I want to send via B, in such a way that when I
get to C, I can receive the files, or issue one or two commands,
and receive all spooled files.

Lets say I ssue the command
uucp file.txt 'B!C!~' to send the file to C via B.

The problem is, once B receives the file, it tries to send it to C,
which may not be online. It just tries and fails, as soon as it
receives it.

Can UUCP be configered to 'test' periodically when C is online, then
send then, or alternatively, can C ping B and get it to send the file?

You could on C, specifically request the file or files, but you'd have
to remember which ones, and what names, but I'm looking for a way to get
those packets flowing once C gets online.

With NNCP, A can just send the file to C via B, and call machine B.
Then C simply calls B and it will receive everything.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 03.05.2025 01:29 Uhr Borax Man wrote:

The problem is, once B receives the file, it tries to send it to C,
which may not be online. It just tries and fails, as soon as it
receives it.

What does fail mean?

Doesn't it queue the file to try later?

Can UUCP be configered to 'test' periodically when C is online, then
send then, or alternatively, can C ping B and get it to send the file?

If that is TCP, such a test should be possible.


--
kind regards
Marco

Send spam to [email protected]

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2025-05-03, Marco Moock <[email protected]> wrote:

On 03.05.2025 01:29 Uhr Borax Man wrote:

The problem is, once B receives the file, it tries to send it to C,
which may not be online. It just tries and fails, as soon as it
receives it.

What does fail mean?

Doesn't it queue the file to try later?

Good question.

The log file /var/log/uucp/Log states

uucico DesktopMachine - (2025-05-03 20:58:00.03 14603) Calling system DesktopMachine (port TCP)
uucico DesktopMachine - (2025-05-03 20:58:22.06 14603) ERROR: connect: No route to host


DesktopMachine is playing the role of "C". At the moment its not powered up.

It may try again later. As long as it tries at some point when the
machine is up, it will work. I'll test that out.

Can UUCP be configered to 'test' periodically when C is online, then
send then, or alternatively, can C ping B and get it to send the file?

If that is TCP, such a test should be possible.

I was wondering whether UUCP had this functionality.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi,

Am 03.05.2025 um 03:29 schrieb Borax Man:

I have a quick question with UUCP. I know how to do this with NNCP,
which is a more modern take on UUCP, but I was wondering whether this workflow is possible with UUCP, using TCP connections.

I have machine B, which is on all the time. Machine A wants to send a
file to machine C, where machine C may not be on the network (its
powered down). Ideally I want to send via B, in such a way that when I
get to C, I can receive the files, or issue one or two commands,
and receive all spooled files.

When you have a machine that is powered on all the time (B in your
example) and a machine that is not (A and C in your example), then it is
common practice to have A and C periodically poll B (usually via cron or something) while B will never poll A or C, it will just store files for
when the systems do poll.

Cheers
Martin

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Thus spake Borax Man <[email protected]>

uucico DesktopMachine - (2025-05-03 20:58:00.03 14603) Calling system DesktopMachine (port TCP)
uucico DesktopMachine - (2025-05-03 20:58:22.06 14603) ERROR: connect: No route to host

This is a TCP/IP connection initiated by running uucico, the UUCP file
transfer daemon. uucico is usually started by a cron job running at
predefined intervals. It will connect to the target system, transfer all
files in the outgoing queue and download all files waiting on the target system. If it is unable to connect, all files in the queue will be
preserved for the next run and removed only after a successful transfer.

I was wondering whether UUCP had this functionality.

UUCP was specifically designed for file transfers between systems that
are not permanently online.

--
Пу́тін — хуйло́
https://www.eternal-september.org

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2025-05-03, Ray Banana <[email protected]> wrote:

Thus spake Borax Man <[email protected]>

uucico DesktopMachine - (2025-05-03 20:58:00.03 14603) Calling system DesktopMachine (port TCP)
uucico DesktopMachine - (2025-05-03 20:58:22.06 14603) ERROR: connect: No route to host

This is a TCP/IP connection initiated by running uucico, the UUCP file transfer daemon. uucico is usually started by a cron job running at predefined intervals. It will connect to the target system, transfer all files in the outgoing queue and download all files waiting on the target system. If it is unable to connect, all files in the queue will be
preserved for the next run and removed only after a successful transfer.

I was wondering whether UUCP had this functionality.

UUCP was specifically designed for file transfers between systems that
are not permanently online.

Thats what I suspected, I just wanted to confirm that I wasn't missing something.

Thank you.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2025-05-03, Martin Burmester <[email protected]> wrote:

Hi,

Am 03.05.2025 um 03:29 schrieb Borax Man:

I have a quick question with UUCP. I know how to do this with NNCP,
which is a more modern take on UUCP, but I was wondering whether this
workflow is possible with UUCP, using TCP connections.

I have machine B, which is on all the time. Machine A wants to send a
file to machine C, where machine C may not be on the network (its
powered down). Ideally I want to send via B, in such a way that when I
get to C, I can receive the files, or issue one or two commands,
and receive all spooled files.

When you have a machine that is powered on all the time (B in your
example) and a machine that is not (A and C in your example), then it is common practice to have A and C periodically poll B (usually via cron or something) while B will never poll A or C, it will just store files for
when the systems do poll.

Cheers
Martin

Having C poll B had the desired result. I wasn't sure it would work,
but experimentation showed it does.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)