root@anomaly.sbs.com (W. Patrick Walsh) (08/18/90)
When attempting to download SLS's from SOSCO, I keep receiving the following message: REQUEST: sosco!/usr/spool/uucppublic/SLS/xnx155.Z --> anomaly!/usr/spool/uucppublic/SLS/xnx155.Z (root) (SYSTEM: sosco) remote access to path/file denied for some SLS's it works, for others, it doesn't. Can someone tell me what I'm doing wrong?
alan@mq.UUCP (Alan H. Mintz) (08/21/90)
In article <2610@anomaly.sbs.com>, root@anomaly.sbs.com (W. Patrick Walsh) writes: > When attempting to download SLS's from SOSCO, I keep receiving the following > message: > > REQUEST: sosco!/usr/spool/uucppublic/SLS/xnx155.Z --> anomaly!/usr/spool/uucppublic/SLS/xnx155.Z (root) > (SYSTEM: sosco) remote access to path/file denied > for some SLS's it works, for others, it doesn't. Can someone tell me what I'm > doing wrong? I believe the correct filenames are: sosco!/usr/spool/uucppublic/SLS/xnx155b01.Z sosco!/usr/spool/uucppublic/SLS/xnx155b02.Z sosco!/usr/spool/uucppublic/SLS/xnx155doc.Z There is a list of all SLSs available also, but the filename escapes me. Question: How does one do (or can one do) a directory of a remote directory (like sosco!/usr/spool/uucppublic/SLS) and retrieve the results via uucp ? -- < Alan H. Mintz | Voice +1 714 980 1034 > < Micro-Quick Systems, Inc. | FAX +1 714 944 3995 > < 10384 Hillside Road | uucp: ...!uunet!mq!alan > < Alta Loma, CA 91701 USA | Internet: alan@MQ.COM >
alan@mq.UUCP (Alan H. Mintz) (08/21/90)
In article <42@mq.UUCP>, alan@mq.UUCP (Alan H. Mintz) writes: > There is a list of all SLSs available also, but the filename escapes me. ^(sosco downloadable - some SLSs are not available by uucp) The list is: sosco!/usr/spool/uucppublic/SLS/info -- < Alan H. Mintz | Voice +1 714 980 1034 > < Micro-Quick Systems, Inc. | FAX +1 714 944 3995 > < 10384 Hillside Road | uucp: ...!uunet!mq!alan > < Alta Loma, CA 91701 USA | Internet: alan@MQ.COM >
news@mcshh.hanse.de (Thomas Wieske) (08/25/90)
root@anomaly.sbs.com (W. Patrick Walsh) writes: >When attempting to download SLS's from SOSCO, I keep receiving the following >message: >REQUEST: sosco!/usr/spool/uucppublic/SLS/xnx155.Z --> anomaly!/usr/spool/uucppublic/SLS/xnx155.Z (root) ^^^ exist this directory in your machine? >(SYSTEM: sosco) remote access to path/file denied Normaly, no.. Your must be create this with mkdir SLS, or.... I'm doing this with: uucp sosco!/usr/spool/uucppublic/SLS/xnx155.Z anomaly!/usr/spool/uucppublic or anomaly!/~ The xnx155.Z-file is received in the .../uucppublic directory. bye... thw -- .-------. ---* Wieske's Crew KG, Netzwerk/Kommunikation/Service/Beratung | \ / | --* \ D-2000 Hamburg 76, Lessingstr.2, Tel.: +49 40 / 2500146 **---- ? - | -* \ \ Th. Wieske, Priv. 2512491 Box/Traily: 259704/259308 // | / \ | __>_>_>____________________thw@mcshh.hanse.de____________________// `-------'
mikes@NCoast.ORG (Mike Squires) (08/28/90)
In article <7948@mcshh.hanse.de> news@mcshh.hanse.de (Thomas Wieske) writes: >root@anomaly.sbs.com (W. Patrick Walsh) writes: > >>When attempting to download SLS's from SOSCO, I keep receiving the following >>message: > >>REQUEST: sosco!/usr/spool/uucppublic/SLS/xnx155.Z --> anomaly!/usr/spool/uucppublic/SLS/xnx155.Z (root) > ^^^ exist this directory in your machine? >>(SYSTEM: sosco) remote access to path/file denied > Normaly, no.. > Your must be create this with mkdir SLS, or.... > When I snarf'd xnx155 there were three files: xnx155.inf, xnx155b01.Z, and xnx155b02.Z.