Great Circle Associates Majordomo-Users
(November 1998)
 

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

Subject: Re: MajorCool problem
From: "Jeffrey Barg" <jbarg @ physiciansnews . com>
Date: Thu, 5 Nov 1998 12:21:03 -0500
To: "Bill Houle" <bhoule @ sparc . sandiegoca . ncr . com>
Cc: "majordomo-users" <majordomo-users @ greatcircle . com>

>Jeffrey Barg said:
>>
>> Perhaps this will provide a clue. I checked a file called
Log.mj_key_cache,
>> which contained the following:
>> /usr/bin/nohup: not found
>> /usr/bin/nohup: not found
>
>Uh...unless you created that Log file via shell redirection while
>debugging, I would question the integrity of your MajorCool install.
>There is no use of 'Log' files or the 'nohup' command anywhere in
>the default distribution. Did you do this yourself, or is it by
>chance some pre-packaged RedHat/FreeBSD/etc port?
>
>--bill
>
I the added "auto cache" patch for Majordomo which rebuilds the key cache
whenever newconfig is executed by Majordomo (contributed by Tom White
<tom@net.msstate.edu> and located in the contrib/ directory of majorcool).
This does not seem to be working either and perhaps this is what created the
log file.

Jeff


Indexed By Date Previous: Re: MajorCool
From: Jesper Maartenson <jesper@maartenson.net>
Next: [?] majordomo error message on install
From: Max Pyziur <pyz@panix.com>
Indexed By Thread Previous: Re: MajorCool problem
From: "Jeffrey Barg" <jbarg@physiciansnews.com>
Next: Re: MajorCool problem
From: "Jeffrey Barg" <jbarg@physiciansnews.com>

Google
 
Search Internet Search www.greatcircle.com