Technical article 104917

uucp(C) no longer starts file transfer immediately.

OpenServer 5.0.0

Written · Last revised

Problem

If a job is queued using uucp(C), and the entry for the remote system in:

/usr/lib/uucp/Systems

has a schedule of "Any", for example:

sysname Any ACU 9600 1234 -\r\d-ogin:-\K\d-ogin:-\K\d-ogin: spam ssword: poo

then uucico(ADM) will not start immediately, as it did in previous releases of SCO UNIX System V/386, SCO Open Desktop or SCO Open Server.

Cause

uucp(C) tries to invoke uucico(ADM) with incorrect arguments. It fails and exits with an unseen usage message.

Solution

To work around this problem, run uusched(ADM) immediately following
uucp(C).  For example:
uucp <host>!/tmp/rmtfile /tmp/lclfile ; /usr/lib/uucp/uusched &
where <host> is the remote host.

SCO is aware of this problem and is working to resolve it in a future release of SCO OpenServer.

See also

uucp(C); Systems(F); uucico(ADM); uusched(ADM)

From the Xinuos technical article database, record 104917. Reproduced with permission. The original is at www.sco.com/ta/104917, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.