> MAJORDOMO ABORT (mj_majordomo)!!
> chown(507, 2, "/usr/local/majordomo/lists/announcements.new"): Operation not permitted
> Sure enough, when I go to /usr/local/majordomo/lists, I see a 0-length
> file owned by user bin and group bin. When I su to majordom, it won't
> allow me to "chmod 507.2 announcements.new"... I get "Operation not
Ooo ooo! I know this one! :-)
The problem is that majordomo creates the new list (minus
the name to be deleted) as follows:
1. create list.new
2. make sure that list.new has the same owner as list
3. copy list to list.new (except the name to be deleted)
4. mv list.new list
(I didn't include all the locking stuff since that isn't
The problem is step 2. list.new is created owned by majordomo,
but list is owned by (my guess) daemon. Since majordomo isn't
running as root, it can't fix this problem. It reports the
above error and exist.
To fix this problem, make sure your "list" file is
owned by majordomo.majordomo and you "list.*" files
are owned by daemon.majordomo.
email@example.com -- http://mars.superlink.net/user/tal -- firstname.lastname@example.org
"You can not solve the problem of people being annoying with technology."