Computer Old Farts Forum
 help / color / mirror / Atom feed
From: rtomek at ceti.pl (Tomasz Rola)
Subject: [COFF] UUCP on macOS / *BSD
Date: Tue, 30 Jun 2020 04:26:33 +0200	[thread overview]
Message-ID: <20200630022632.GA21942@tau1.ceti.pl> (raw)
In-Reply-To: <7aff4a42-0109-2278-c573-7e29e878cd57@tnetconsulting.net>

On Mon, Jun 29, 2020 at 02:06:04PM -0600, Grant Taylor via COFF wrote:
> On 6/29/20 11:20 AM, Clem Cole wrote:
> >I can try to pull some info from long ago paged out memory.
> 
[...]
> I'm trying to ""dial out from macOS into Linux.
> 
> Saying "trying" is somewhat of a misnomer as it is working perfectly
> when I run uucico as the _uucp user.
> 
> The only apparent problem is related to users other than the _uucp
> user prompting the call.  I need to do some more investigating on
> this.
> 
> I can initiate actions as my normal user; uucp, uuto, etc. and they
> properly queue actions.  They also spur a call, which fails.  If I
> subsequently spur a call as the _uucp user, things work perfectly
> fine.
[...]

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.

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

-- 
Regards,
Tomasz Rola

--
** A C programmer asked whether computer had Buddha's nature.      **
** As the answer, master did "rm -rif" on the programmer's home    **
** directory. And then the C programmer became enlightened...      **
**                                                                 **
** Tomasz Rola          mailto:tomasz_rola at bigfoot.com             **


  parent reply	other threads:[~2020-06-30  2:26 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 [this message]
2020-06-30  3:19           ` gtaylor
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=20200630022632.GA21942@tau1.ceti.pl \
    --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).