>>>>> "CM" == Chuck Milam <milam@uwosh.edu> writes:
CM> I'm double-checking to make sure I have the logs set up corretly, and
CM> that the debug level is set high (500 is the max debug level, right?)
The max level is infinite. Above 500 only debugs SMTP and some trivial
stuff.
CM> I'm not sure I understand the proper way to use the "post" command from
CM> the command line interface:
So, maybe post isn't working. But how about some other operations on the
affected lists? Does 'who' work, for example (since it plows through the
database in the same manner that posting does)?
The fact that the logging stopped running would really suggest a disk
filling up. Opening the log and writing the startup message is the first
thing that happens (besides the Perl startup and compilation and the
command line parsing, of course).
- J<
Follow-Ups:
References:
|
|
