Computer Old Farts Forum
 help / color / mirror / Atom feed
From: gtaylor at tnetconsulting.net (Grant Taylor)
Subject: [COFF] UUCP on macOS / *BSD
Date: Mon, 29 Jun 2020 21:19:20 -0600	[thread overview]
Message-ID: <76024752-a506-abf1-1990-0b66630bb7db@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <20200630022632.GA21942@tau1.ceti.pl>

On 6/29/20 8:26 PM, Tomasz Rola wrote:
> So, assuming that I understood your problem
>   - and given that I know close to nothing about uucp
>   - and given that I know close to nothing about MacOS pecularities
> 
> I wonder if your problem could be solved by setting up a small crontab 
> entry for user _uucp, where a script would be called every minute 
> and check, if there is previous instance of it running and if there 
> are some jobs in the queue, and do the stuff when the answer were no 
> and yes, respectively.

You're quite close to what I've seen on other systems.  It would 
probably also work on the current problem system as a work around.  But 
I don't think it will solve the underlying problem.

There is an underlying utility that's part of the UUCP suite named 
"uucico" and it's job is to connect to itself and transfer files.  It 
has a function where it will see if there is any work (UUCP terms) and 
if there is, do it.

So I've frequently seen uucico run on an hourly cron job on a number of 
systems.

I do believe that would work around the problem.

I'm trying to understand what the problem is that is actually happening 
so that I can use things properly and not need to rely on the workaround.

Incidentally, other Linux systems running the same software with the 
same config don't need the workaround.  :-|

> Special user moving files over ssh, normal users putting files in 
> the queue.

There's some more nuance to it than that.  But, sure, that's the gist of it.

Subsystem that runs as a dedicated user moving files between systems, 
over SSH in this case.  Normal users use other commands to ask said 
subsystem to do work on their behalf.

Said subsystem includes creating and managing a queue structure, 
determining if / when to connect (call) a remote system, transferring 
files both ways, dealing with failures, and retrying.

Oh, ya, said subsystem is an industry standard across most Unixes and 
some other platforms.



-- 
Grant. . . .
unix || die

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4013 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200629/aa3afdb7/attachment.bin>


  reply	other threads:[~2020-06-30  3:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-29  0:50 gtaylor
2020-06-29 15:37 ` lm
2020-06-29 16:13   ` gtaylor
2020-07-05  6:30   ` dave
2020-06-29 15:53 ` arrigo
2020-06-29 16:42   ` gtaylor
2020-06-29 17:20     ` clemc
2020-06-29 20:06       ` gtaylor
2020-06-29 20:59         ` clemc
2020-06-30  2:26         ` rtomek
2020-06-30  3:19           ` gtaylor [this message]
2020-06-30  3:26             ` rtomek
2020-06-30  3:46               ` rtomek
2020-06-30  3:50                 ` gtaylor
2020-06-30  3:47               ` gtaylor
2020-06-29 17:22     ` arrigo
2020-06-29 20:18       ` gtaylor
2020-06-29 20:31         ` gtaylor
2020-07-01 17:32 ` gtaylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=76024752-a506-abf1-1990-0b66630bb7db@spamtrap.tnetconsulting.net \
    --to=coff@minnie.tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).