>I see, do I need to make that file executable and how?

>/usr/lib64/bacula # ll

>total 180

>-rwx------ 1 root bacula   938 Jan 15 13:50 bacula-password-setup.sh

>-rwxr-xr-x 1 root bacula   486 Jan 15 13:50 bconsole

>-rwxr-xr-x 1 root bacula 32449 Jan 15 13:50 bpipe-fd.so

>-rw-r--r-- 1 root bacula   341 Jan 15 13:50 btraceback.gdb

>-rwxr-xr-x 1 root bacula   734 Feb 11 17:56 create_bacula_database

>-rwxr-xr-x 1 root root     291 Jan 15 13:50 create_mysql_database

Yours are marked executable, although they use a different set of permissions than mine. They use a different Group than mine too.

Unfortunately, I have found that these settings can differ greatly from one distro to another. They also vary by whomever created the package. People get used to using certain directories and continue to use them even though everyone else is using other directories.

For example, I use Ubuntu and the scripts are placed in /etc/bacula/scripts/* 

I compile bacula from source, so I have to tell the installer to place them there. And the reason I place them there is because that seems to be the directory most commonly used for Ubuntu.

Anyway, the point I'm making is that the permissions you see on your computer may be correct, and you shouldn’t change them at this point...