diff options
author | Laurent Bercot <ska-skaware@skarnet.org> | 2023-02-05 23:32:05 +0000 |
---|---|---|
committer | Laurent Bercot <ska@appnovation.com> | 2023-02-05 23:32:05 +0000 |
commit | 9c2bebec16aafefb9067c1db83ef3c765e13610b (patch) | |
tree | 35d516abd5d3aeb089a8c2b0bc99532bb1ce6a30 /INSTALL | |
parent | 4676457df2c8a73b4f589a66315b9b137ee89202 (diff) | |
download | execline-9c2bebec16aafefb9067c1db83ef3c765e13610b.tar.xz |
Document execline and multicall
Signed-off-by: Laurent Bercot <ska@appnovation.com>
Diffstat (limited to 'INSTALL')
-rw-r--r-- | INSTALL | 9 |
1 files changed, 4 insertions, 5 deletions
@@ -177,7 +177,7 @@ are small, so it does not cost much to duplicate the entire source tree if parallel builds are needed. -* Multicall binary - THIS IS EXPERIMENTAL. +* Multicall binary ---------------- Starting with version 2.9.2.0, the execline package comes with an @@ -188,10 +188,9 @@ called with, or the subcommand it is given: "execline cd / true" will chdir to / before exiting, same as "cd / true" if cd is a link to the execline program. - To use this, after invoking configure, type: make multicall - You can strip the binary with: make multicall-strip - You can install it with: make multicall-install - Be aware that it will overwrite a previous installation. + To use this, use the --enable-multicall option to configure. Only +the execline binary will be built, and other programs will be +created as symbolic links to execline at installation time. The multicall setup saves a lot of disk space, at the price of am unnoticeable amount of CPU usage. RAM usage is about equivalent |