>
> This seems to be a common problem for alot of newcomers to majordomo.
It Sure is for me!
>
> I'm not sure if the solution is in the FAQ, but here it is:
>
> The reason majordomo takes forever to act upon any requests is most likely
> due to improper installation.
Yep, almost all my Unix problems are caused by my lack of knowledge.
(newbie!)
>Most directly, it's because the W_UID
> and W_GID entries were not changed to correspond to the UID and GID
> of YOUR MAJORDOMO USER ACCOUNT! Once you create the majordom
> group and user take a look at your password file and record the UID
> and GID of YOUR majordom user & groupd entry. Edit the Makefile
> and make the appropriate changes, save Makefile, run make, then
> make install-wrapper. I almost guarantee that this will clear up
> 99.9999999999999% of the problems with perl churning away on a majordomo
> request.
Darn! why do I have to be the exception!? My UID/GID are exactly the
same in the makefile as defined in etc/passwd, yet majordomo requests
crunch almost forever. And finally end with the imfamous "Out of
Memory" error message. I have read the FAQ at least four times &
can find no reason that Perl 4.036/Majordomo V1.93 would behave
this way. I'm sure that it's a dumb error on my part, but cannot
*FIND* it...??
johnd
--IAB05804.796486912/freeware.aus.sps.mot.com--
|
|
