Take the 2-minute tour ×
Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems.. It's 100% free, no registration required.
source some_file

some_file:

doit ()
{
  echo doit $1
}
export TEST=true

If I source some_file the function "doit" and the variable TEST are available on the command line. But running this script:

script.sh:

#/bin/sh
echo $TEST
doit test2

Will return the value of TEST, but will generate an error about the unknown function "doit".

Can I "export" the function, too, or do I have to source some_file in script.sh to use the function there?

share|improve this question
2  
summarizing answers below (enzotib is correct, assuming you can use bash, as the question indicates): change #!/bin/sh to #!/bin/bash and after doit() {...} just export -f doit –  michael_n Jun 11 '13 at 21:08
add comment

4 Answers

up vote 23 down vote accepted

In bash you can export function definitions to sub-shell with

export -f function_name

For example you can try this simple example:

./script1:

    #!/bin/bash

    myfun() {
        echo "Hello!"
    }

    export -f myfun
    ./script2

./script2:

    #!/bin/bash

    myfun

Then if you call ./script1 you will see the output Hello!.

share|improve this answer
add comment

Functions are not exported to subprocesses. This is why there are files named .kshrc or .bashrc: To define functions that shoiuld be available in subshells also.

If running a script, the .*shrc scripts are normally not sourced. You would have to code that explicitly, like in . ~/.kshrc.

share|improve this answer
    
So the ~root/.bashrc could be an option in my case, since the scripts are run as root. Thanks for that hint. –  Nils Oct 17 '11 at 19:06
    
if using the .*shrc files, be sure they dont force interactive behaviour (like the stupid alias rm=rm -i) –  ktf Oct 18 '11 at 8:50
add comment

You cannot export functions, not in the way that you are describing. The shell will only load the ~/.bashrc file on the start of an interactive shell (search for "Invocation" in the bash manpage).

What you can do is create "library" which is loaded when you start the program:

source "$HOME/lib/somefile"

And place your non-interactive functions and settings there.

share|improve this answer
    
So I have to either start the subshell with the "login" parameter (to parse ~/.profile) or source that file. –  Nils Oct 17 '11 at 19:11
    
Looking a little more closely, on non-interactive shells, you could set BASH_ENV environment variable to some_file you already have, and it would be called. It would be easy enough to find that out: echo echo foobar > /tmp/foobar; BASH_ENV=/tmp/foobar $SHELL -c : –  Arcege Oct 17 '11 at 19:20
add comment

well, i'm new in linux, but you can try this:

in some file, let's call it: 'tmp/general' you build your function:

func1(){
   echo "func from general"
}

in your shell script add :

. /tmp/general

and run:

func1

you'll get on the screen: "func from general"

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.