Hi again Jason,
I've installed perl 5 and I tested your script. I got the proper UID so
it looks like wrapper isn't my culprit. Any idea where I should look now?
I'm really confused since my setup had been working for months. I added
some development libraries to my system and POOF majordomo is busted.
jim
##################################
## James V. Lentini ##
## Systems Analyst ##
## Voice:303.275.2414 ##
##################################
On 8 Aug 1996, Jason L Tibbitts III wrote:
> >>>>> "JL" == Jim Lentini <lentinij@dataadmin.irm.r9.fws.gov> writes:
>
> JL> Now the wrapper binary runs eternally. And I have to rm resend in order
> JL> to stop the process.
>
> Are you certain that the wrapper spins forever? Or is the process that the
> wrapper spawns spinning?
>
> Try putting the following:
>
> #!/usr/local/bin/perl5
> print "$<\n$>\n";
>
> as id.pl in the same directory as the wrapper, and make it executable. Run
> it like this:
>
> XYX:sina:~/lists/majordomo> ./id.pl
> 7225
> 7225
>
> XYX:sina:~/lists/majordomo> ./wrapper id.pl
> 101
> 101
>
>
> That gives a basic check that the wrapper is working; the first output
> should be your uid, the latter should be your majordomo user's uid.
> Different OSes may differ slightly, but the invocation under wrapper should
> always change one of the numbers.
>
> JL> What are some factors that would cause resend to not die?
>
> If resend is spinning, the general cause is a permission problem that
> causes it to not be able to lock the files it needs. 1.93 can get into an
> infinite loop, continually consuming memory. 1.94 is better in that
> respect.
> --
> Jason L. Tibbitts III - tibbs@uh.edu - 713/743-8684 - 221SR1
> System Manager: University of Houston High Performance Computing Center
> 1994 PC800 "Kuroneko" DoD# 1723
>
References:
|
|
