Hello,
OK, yes, it makes sense that the systemd directory code was probably
implemented at the same time as the systemd files. Simone is going to
give me some enhanced systemd files, and I will add an appropriate
Makefile target for getting them installed.
Thanks for bringing this up.
Best regards,
Kern
On 11/07/2014 01:57 PM, Can Şirin wrote:
> Quoting Kern Sibbald <kern AT sibbald DOT com>:
>
>> Hello,
>>
>> Yes, you are correct, currently there is no Makefile command to install
>> the systemd files. I like your idea of adding a new configure option.
>> I would probably prefer "with-systemd-dir=" which corresponds to how the
>> other directories work, then define a default and as you say just add a
>> new Makefile target -- probably "make install-systemd".
>
> Actually, this is not my idea. Systemd support has already been added
> to configure script. So I just wanted to use it.
>
> [root@bacula bacula-7.0.5]# ./configure --help | grep systemd
> --with-systemd[=UNITDIR]
> Include systemd support. UNITDIR is where
> systemd
> [root@bacula bacula-7.0.5]#
>
>>
>> It sounds like a nice little project that is needed and not too hard to
>> implement.
>>
>> Have you done any of the work to accomplish this, or are you asking me
>> or someone else to do it?
>>
>
> I haven't done anything. Because there are generic systemd files under
> the source code directory tree whose path is exactly
> bacula-7.0.5/platforms/systemd/
> I can copy them from this path manually.
> So, for now, I am going on with the SysV init scrit until you
> implement it.
>
> Kind regards.
> Can
>
>> Best regards,
>> Kern
>>
>> On 11/07/2014 09:07 AM, Can Şirin wrote:
>>> Hi,
>>>
>>> I am setting up a new backup server with Bacula 7.0.5 on RHEL7. I am
>>> going to
>>> compile it from the source code. Everything is fine but just systemd
>>> integration.
>>>
>>> In the configuration options, I use
>>> "--with-systemd=/usr/lib/systemd/system"
>>>
>>> After "make" command has been ended, I run the "make install" but
>>> unfortunately
>>> there is no systemd unit file copied by the bacula installation
>>> under the
>>> /usr/lib/systemd/system directory.
>>>
>>> I thought it was needed to run "make install-autoconf". With this way
>>> only SysV init files are copied.
>>>
>>> How could I install the systemd unit files, without copying them
>>> manually from the source (platform/systemd) dir?
>>>
>>> My configure options are;
>>>
>>> CFLAGS="-g -Wall" ./configure \
>>> --sbindir=/opt/bacula/bin \
>>> --sysconfdir=/opt/bacula/etc \
>>> --enable-smartalloc \
>>> --with-postgresql=/usr/pgsql-9.3 \
>>> --with-working-dir=/opt/bacula/working \
>>> --with-pid-dir=/opt/bacula/working \
>>> --with-subsys-dir=/opt/bacula/working \
>>> --with-openssl \
>>> --enable-conio \
>>> --with-openssl \
>>> --enable-acl \
>>> --enable-lzo \
>>> --enable-lockmgr \
>>> --with-tcp-wrappers \
>>> --with-dir-user=bacula \
>>> --with-dir-group=bacula \
>>> --with-sd-user=bacula \
>>> --with-sd-group=bacula \
>>> --enable-bat \
>>> --with-systemd=/usr/lib/systemd/system
>>>
>>> Thanks,
>>> Can
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> Bacula-users mailing list
>>> Bacula-users AT lists.sourceforge DOT net
>>> https://lists.sourceforge.net/lists/listinfo/bacula-users
>>>
>
>
>
------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
