Section 3 : Running a Server

Q351: UUCP locking in Solaris x86, ...

? Got something to say about this answer? Hit the question mark to invoke the mailer and send your comments to the HylaFAQ maintainers.

UUCP locking in Solaris x86, ...

Date: Tue, 4 Jun 1996 07:45:08 +0200 (MST)
From: Matthias Apitz < >
Subject: Re: incomming faxing in Solaris x86... wrote:
    Hi again,
    Well I've got outgoing faxes under control completely however, I can't
    get faxgetty to coexist with dp-4.0 
    Does this inittab look correct? ie. is the device correct?
    t2:23:respawn:/usr/local/sbin/faxgetty  ttyb
    dp-4.0 uses cuab or cua1 in bsd terms...

UUCP lock files are based on the major number of the device
containing the entry of the tty special files and the
major and minor number of the tty special itself. These
numbers are used to create the name of the lock file and
the pid of the locking proc is written into this file in ascii or
binary. See the example below:

$ cat /var/spool/locks/LK.047.071.080
$ ls -l /dev/root
brw-------   2 root     sys       47,  1 Aug 13  1994 /dev/root
$ ls -l /dev/ttyFN01
crw-rw-rw-   1 uucp     uucp      71, 80 Jun  4 07:14 /dev/ttyFN01

Both ("dp" and faxgetty) must use the same locking style (ascii
or binary) and the same numbers generated from the names dev/ttyb
and dev/cuab.  Does these two special files have the same major and minor?


 Back to FAQ Index FAQ Index  Next question in List Q352: AT+FAP=? gives ERROR? Last updated $Date: 2000/01/10 00:56:31 $.