![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to AppendixII CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [Research Unix] / researchv10no / cmd / uucp / doc / admin|
Return to AppendixII CVS log | Up to [Research Unix] / researchv10no / cmd / uucp / doc / admin |
1.1 root 1: .P
2: These are the ASSERT error messages that can occur.
3: The will appear in the error log (/usr/spool/uucp/.Admin/errors).
4: When the errors occur, the program will abort--the file name,
5: sccsid, line number will appear in the error message along with the
6: following text.
7: In most cases, these result from file system problems;
8: use the errno, when present to check out the problem.
9: .P
10: .VL 23 0
11: .LI "CAN'T OPEN"
12: An open() or fopen() failed--``errno'' appears in ()
13: .LI "CAN'T WRITE"
14: A write() or fwrite() or fprintf() etc--``errno'' appears in ()
15: .LI "CAN'T READ"
16: A read(), fgets(), etc failed--``errno'' appears in ()
17: .LI "CAN'T CREATE"
18: A creat() call failed--``errno'' appears in ()
19: .LI "CAN'T ALLOCATE"
20: A dynamic allocation failed.
21: .LI "CAN'T LOCK"
22: An attempt to make a LCK (lock) file failed.
23: In some
24: cases, this is a fatal error.
25: .LI "CAN'T STAT"
26: A stat() call failed--``errno'' appears in ()
27: .LI "CAN'T CHMOD"
28: A chmod() call failed--``errno'' appears in ()
29: .LI "CAN'T LINK"
30: A link() call failed--``errno'' appears in ()
31: .LI "CAN'T CHDIR"
32: A chdir() call failed--``errno'' appears in ()
33: .LI "CAN'T UNLINK"
34: A unlink() call failed--``errno'' appears in ()
35: .LI "WRONG ROLE"
36: This is an internal logic problem.
37: .LI "CAN'T MOVE TO CORRUPTDIR"
38: .br
39: An attempt to move some bad C. or X. files
40: to the .Corrupt directory failed--the directory is
41: probably missing or has wrong modes or owner.
42: (/usr/spool/uucp/.Corrupt)
43: .LI "CAN'T CLOSE"
44: A close() or fclose() call failed--``errno'' appears in ()
45: .LI "FILE EXISTS"
46: The creation of a C. or D. file is attempted, but the file exists.
47: This
48: occurs when there is a problem with the sequence file
49: access--usually a software error.
50: .LI "No uucp server"
51: A tcp/ip call is attempted, but there is no server for uucp.
52: .LI "BAD UID"
53: The uid can not be found in the /etc/passwd file.
54: The file system is in trouble, or the /etc/passwd file is inconsistant.
55: .LI "BAD LOGIN_UID"
56: same as previous.
57: .LI "ULIMIT TOO SMALL"
58: The ulimit for the current user/process is too small;
59: file transfers may fail, so transfer is not
60: attempted.
61: .LI "BAD LINE"
62: There is a bad line in the Devices file;
63: there are not enough arguments on one or more lines.
64: .LI "FSTAT FAILED IN EWRDATA"
65: .br
66: There is something wrong with the ethernet media.
67: .LI "SYSLST OVERFLOW"
68: An internal table in gename.c overflowed.
69: A big/strange request was attempted--send it with MR to the
70: appropriate place.
71: .LI "TOO MANY SAVED C FILES"
72: .br
73: same as previous
74: .LI "RETURN FROM fixline ioctl"
75: .br
76: An ioctl, which should never fail, failed.
77: There is a system or driver problem.
78: .LI "BAD SPEED"
79: A bad line speed appears in the Devices/Systems files.
80: .LI "PERMISSIONS file: BAD OPTION--"
81: .br
82: There is a bad line or option in the PERMISSIONS file.
83: Fix it immediately!
84: .LI "PKCGET READ"
85: The other side probably hung up;
86: don't worry about it.
87: .LI "SYSTAT OPEN FAIL"
88: There is a problem with the modes of /usr/lib/uucp/.Status, or there
89: is a file with bad modes in the directory.
90: .LI "TOO MANY LOCKS"
91: There is some internal problem!
92: Send in an MR.
93: .LI "CAN NOT ALLOCATE FOR"
94: .br
95: There is some kernel problem;
96: a call to calloc() failed.
97: .LI "XMV ERROR"
98: There is a problem with some file or directory;
99: It is likely the spool directory, since the modes of
100: the destinations were suppose to be checked before
101: the program attempts this.
102: .LI "CAN'T FORK"
103: An attempt to fork and exec failed.
104: The current job should not be lost, but will be attempted later
105: (uuxqt).
106: No action need be taken.
107: .LE
108: .SK
109: These are the messages that will appear in the system status file:
110: .VL 23 0
111: .LI "OK"
112: Things are OK.
113: .LI "NO DEVICES AVAILABLE"
114: There is no currently available device for the call.
115: Check to see that there is a valid device in Devices file
116: for this system.
117: .LI "WRONG TIME TO CALL"
118: self explanatory
119: .LI "TALKING"
120: self explanatory
121: .LI "SOME FAILURE"
122:
123: to be determined
124: .LI "BAD SEQUENCE CHECK"
125: If sequence checking is used between systems, the
126: sequence numbers do not agree. (This is almost never
127: used.)
128: .LI "CALLER SCRIPT FAILED"
129: The negotiations with the modem/network specified in the
130: DIALERS file did not complete successfully.
131: This is similar to DIAL FAILED.
132: I may occassionally fail, but if it never succeeds, there may
133: be a problem with the entry in the DIALERS file.
134: .LI "LOGIN FAILED"
135: The login for the given machine failed.
136: It could
137: be a wrong login/passwd, wrong number, a very slow
138: machine, or failure in getting through the chat script.
139: .LI "CONVERSATION FAILED"
140: The conversation failed after successful startup.
141: This usually means that one side went down, the program
142: aborted, or the line just hung up.
143: .LI "DIAL FAILED"
144: The remote never answered.
145: It could be a bad dialer or
146: the wrong phone number.
147: .LI "BAD LOGIN/MACHINE COMBINATION"
148: .br
149: The machine called us with login/machine name
150: that does not agree with our PERMISSIONS file.
151: They could be trying to masquerade!
152: .LI "DEVICE LOCKED"
153: The calling device is currently locked and in use
154: by some process.
155: .LI "ASSERT ERROR"
156: An ASSERT error occurred--see
157: /usr/spool/uucp/.Admin/errors.
158: .LI "SYSTEM NOT IN Systems"
159: The system name is not in Systems.
160: .LI "CAN'T ACCESS DEVICE"
161: The device tried does not exist,
162: or the modes are wrong.
163: .LI "DEVICE FAILED"
164: The open of the device failed.
165: .LI "WRONG MACHINE NAME"
166: The called machine is reporting a different
167: name in the Shere= message.
168: .LI "CALLBACK REQUIRED"
169: The called machine requires that it call us.
170: .LI "REMOTE HAS A LCK FILE FOR ME"
171: .br
172: The remote site has a LCK file for this
173: system.
174: They could be trying to call us.
175: If they have an older version of uucp, the process
176: that was talking to us may have failed leaving the
177: LCK file.
178: If they have the new uucp, and they are
179: not trying us, then the process that was talking to
180: us is hung!
181: .LI "REMOTE DOES NOT KNOW ME"
182: .br
183: The remote site does not have our name in their
184: Systems file.
185: .LI "REMOTE REJECT AFTER LOGIN"
186: .br
187: The login we used does not correspond to what
188: the remote site is expecting.
189: .LI "REMOTE REJECT, UNKNOWN MESSAGE"
190: .br
191: The remote site rejected us for unknown
192: reason--they are probably not running a standard
193: version of uucp.
194: .LE
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.