:: Re: [DNG] Init scripts in packages
Top Page
Delete this message
Reply to this message
Author: Rainer Weikusat
Date:  
To: dng
Subject: Re: [DNG] Init scripts in packages
Rainer Weikusat <rainerweikusat@???> writes:
> Laurent Bercot <ska-devel@???> writes:
>> On 06/08/2015 20:18, Rainer Weikusat wrote:
>>> UNIX(*) and therefore, Linux, provides two system calls named fork and
>>> exec which can be used to create a new process while inheriting certain
>>> parts of the existing environment and to execute a new program in an
>>> existing process, keeping most of the environment. This implies that it
>>> is possible to write a program which performs a particular 'environment
>>> setup task' and then executes another program in the change
>>> environment.
>
> [...]
>
>>> And that's finally the jboss start script. I have some more tools of
>>> this kind because whenever I need a new, generic process management task
>>> to be performed, I write a new program doing that which can be used in
>>> concert with the existing ones.
>>
>> What you are saying is that your approach is exactly the same as the
>> one found here:
>> http://skarnet.org/software/execline/
>
> No, it's not. This is an interpreter for another programming language
> sharing some concepts with the Thompson-shell.


For the sake of accuracy: While this calls itself an interpreter, it
actually isn't. It's a compiler generating threaded code for immediate
execution upon call. It's sort-of similar to the Thompson-shell because
it relies on separate programs for providing any 'real' functionality,
including 'control constructs'.