> Stephen P Potter <email@example.com> writes:
># Strange sunspot activity caused firstname.lastname@example.org (Bill Silvert) to write
> # | This message is being processed at the rate of about two commands per
> # | hour. It should take about three days for all 160 users to be
> # | unsubscribed!
> # |
> # One thing I did find out about my slowdown is that the directory where the
> # log file was being written didn't have the proper permissions. (Majordomo
> # wasn't reporting that at the time). Once I figured that out, things
> # started to speed up. Now, requests are almost instantanious.
> Yeah, that would definitely explain a major slowdown. Majordomo would
> try to lock the log file (by creating a lock file in the directory
> with the log file) for 10 minutes for each log message, before giving
> up. It's typically going to log one log message for each command in
> the input.
I am new to this mailing list. I am installing majordomo on our server
and am only doing tests right now. I have a SparcServer 1000 running
Solaris 2.3. I have had the same problem with the program taking a long time
to process requests. Right now I have only sent a "help" command and it
takes well over half an hour to process the message.
The message coped above is from the archive directory. In several messages
permissions of the Log file were talked about, but no on specifed what the
correct permissions are. Could someone tell me this? Also, should everything
in my majordomo directory by owned by majordom and the group set to
Thanks so much for you help.