home *** CD-ROM | disk | FTP | other *** search
- lpr RISC-OS Port
- ================
-
- Known deviations from RFC1179
- -----------------------------
-
- 1. lpr always sends the control file second.
- 2. The source port of the connection is allocated from the
- auto allocate block in the normal way, as a result the source
- port will never be in range 721-731 as spec'd by the RFC.
- 3. The range of job numbers produced is only 000 to 256.
- 4. No checking is made on the variable lpr$usr which is used for the
- control file username, as a result that variable must not start
- with a digit. If it does not exist it is set by lpr to 'root'.
-
-
- Other points...
- ---------------
-
- The control file only exists in memory during the execution of lpr.
- The entries for the file come from the RISC-OS envoirment variables, as
- such the the hostname is taken from the variable Inet$Hostname.
-
- It is worth noting that the author is currently aware of a 'feature' in
- the OS/2 Warp version on lpd, which means it will also print the 'control
- file', when started without any switches, the useful switches are:-
-
- /? - display usage details.
- -b - only print banner if supplied by client (I never supply
- a banner so this turn banners form us off).
-
- -c - Don't Print control file. You'll probaly want to use this.
- -s - only accept connections form port 721-731, you can't use
- this option is your using this client.
-
-
- --
- Roger G Gammans
- rgammans@compsurg.demon.co.uk