[BusyBox] Running app from inittab script vs /bin/sh

[Wolfgang Denk]

In message <1070930105.5181.14.camel at localhost.localdomain> you wrote:
> 
> I have an application that runs fine when I run it from the shell but
> turns into zombies when I run it from a shell started from inittab.
> 
> Works:
> 
> # /home/myapp

Does it actually work that way in the ramdisk environment, or did you
only test it in a NFS-root world?

Are you sure that all needed libraries have been added to the ramdisk
image?

> In trying to figure out what is going on, when I try to give it a
> terminal by invoking it as:
> 	
> 	/bin/sh /home/myapp
> 
> I get the following error message (which is even more suspect):
> 	
> 	.ELF...: not found

This is not suspect, but what happens if you try to run an ELF binary
file as a shell script. Don't do it, then.

> FWIW, the application spawns a bunch of threads and uses some shared
> memory IPC constructs (semaphores, message queues, etc.).  It was built
> statically so there are no dynamic library issues going on.

Don't bet on this. Some libraries use dlopen()  to  dynamically  load
additional stuff even if linked statically.

> Has anybody else seen this problem?

Likely problems: (1) a bug in your application, (2) missing libraries
and/or other relevant files, (3) missing shm  support,  (4)  shm  not
mounted, ...


Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
Accident: A condition in which presence of mind is good, but  absence
of body is better.