Fri, 03 Aug 2012 20:11:53 +0200
Neutralize buggy code causing OpenPKG to have 'fatal problems' in
spite of correct installation, configuration, and operation. An
administrator suffering from this failure is even unable to
uninstall the flawed software.
1 #!/bin/sh
2 myName=`basename $0`
3 cfgPath="@l_prefix@/etc/bacula"
4 case "$myName" in
5 bacula-dir ) cfg="bacula-dir.conf" ;;
6 bacula-fd ) cfg="bacula-fd.conf" ;;
7 bacula-sd ) cfg="bacula-sd.conf" ;;
8 bconsole ) cfg="bconsole.conf" ;;
9 bcopy ) cfg="bacula-sd.conf" ;;
10 bextract ) cfg="bacula-sd.conf" ;;
11 bls ) cfg="bacula-sd.conf" ;;
12 bscan ) cfg="bacula-sd.conf" ;;
13 dbcheck ) cfg="bacula-dir.conf" ;;
14 tray-monitor ) cfg="tray-monitor.conf" ;;
15 wx-console ) cfg="wx-console.conf" ;;
16 * ) echo "bexec: illegal link to '$0'" 1>&2; exit 1 ;;
17 esac
18 cfg="$cfgPath/$cfg"
19 # The user is still able to specify own config files, because
20 # the commands accept multiple '-c' options. The last '-c' wins.
21 exec @l_prefix@/libexec/bacula/$myName -c $cfg "$@"