Great Circle Associates Majordomo-Workers
(July 1997)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Solved: [Fwd: Help! I'm Stumped]
From: Russ McClay <mcclay @ taolodge . com . tw>
Organization: Tao Lodge China
Date: Mon, 28 Jul 1997 21:44:04 +0800
To: majordomo-workers @ greatcircle . com
Reply-to: mcclay @ taolodge . com . tw

I posted the following problem which I have now solved,
though not to the degree I would like: 

Russ McClay wrote:
 
> I have run Majordomo successfully before...but just now
> upgraded from 1.90 to 1.94.3 and have a strange problem
> with unsubscribing:
> 
> Environment:
> 
> Linux 1.2.8
> Perl 4.036
> Majordomo 1.94.3
> 
> What happens is I get an abort with this message:
> 
> ABORT chown(524, 2, "/usr/local/majordomo/lists/test.new"): 
> Operation not permitted
> 
> What I see is the user "bin" is running this process and creates
> two files in the lists directory: test.new and L.test
> 
> The owner/group is "bin" and then when it tries to chown it seems
> to do so as majordom which doesn't have sufficient rights to
> change what "bin".
> 
> The config-test checks out fine.  I can subscribe to lists,
> I can post to lists, everything except UNSUBSCRIBE!
> 
> I've spent two days re-installing, re-reading all the documents,
> doing searches on both the majordomo-users and majordomo-workers
> archives and I can't see anyone who has had this problem, though
> one message came close (to describing a similar problem).

The solution to my problem was to place the user of the
majordomo account (which is majordom) into the group "bin".

I had originally created a new group also called majordom into
which I placed user majordom. But after I ran into the unsubscribe 
problem I deleted the group and placed the user majordom into 
the daemon group (which on my system also includes "bin"). That
didn't solve the problem either. 

But by placing majordom into the bin group, the problem
went away. However, it seems not many people have run into
this problem.  My limited knowledge of the inner workings
of Majordomo lead me to believe there is something funny
going on with the wrapper and my rather outdated sendmail  
(v.8.6.9.2).

I might add that during the process of solving the problem
I re-explored what alternatives exist out there in regard
to list servers for Linux.  I again determined that Majordomo
was the best solution...which forced me to solve the 
unsubscribe problem. 

FWIW.  Thanks to those who replied to my original plea
for help.

Russ McClay
Taipei, Taiwan



Indexed By Date Previous: Re: Help! I'm Stumped
From: Dave Wolfe <dwolfe@risc.sps.mot.com>
Next: *Please HELP ASAP!*
From: scotcm@map.com (Charles MacLaurin)
Indexed By Thread Previous: Re: Help! I'm Stumped
From: Dave Wolfe <dwolfe@risc.sps.mot.com>
Next: *Please HELP ASAP!*
From: scotcm@map.com (Charles MacLaurin)

Google
 
Search Internet Search www.greatcircle.com