Hello,
It is working now.
The install.cfg contains the lines:
command=/dist/script_a
system
However, I was wondering if there are any restrictions in terms of what
can be launched.
From the script that is launched by the `system` command (script_a) I am
generating a second script (/tmp/script_b) and try to execute it (/bin/sh
/tmp/script_b)
The generation and execution of script B is done within an "until" cycle
and requires
input from the user.
Although the whole stuff (script A which generates and runs script B) runs
OK in
normal circumstances, when it is launched by the `system` command it seems
that
it enters an infinite cycle generating and executing script B.
Any ideas would be much appreciated.
Thanks,
Florentin Albu
Client-Server Systems Manager
falbu@amnesty.org
_________________________________________________________
Amnesty International, International Secretariat
visit us at http://www.amnesty.org
Be Realistic! Plan for a Miracle!
ONE click to stamp out torture.
http://www.stoptorture.org
Jordan Hubbard <jkh@winston.osd.bsdi.com>
Sent by: owner-freebsd-config@FreeBSD.ORG
17/02/2001 00:33
To: floral@care4free.net
cc: freebsd-config@FreeBSD.ORG
Subject: Re: 'system' function in install.cfg
> However, I want to execute a small script before restarting the system .
> I am using the "system" function in install.cfg. For testing purposes I
> was trying to launch a shell with it.
>
> [...]
> installCommit
> system /bin/sh
> shutdown
There's no argument passing supported with install.cfg (I know, yuck)
which is why everything is done through the variable space. The
system command takes the string to execute in the "command" variable.
- Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-config" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-config" in the body of the message