[QUOTE=malcolmlewis;2747406]Project Configuration of home:gody - openSUSE Build Service
compared to;
Project Configuration of home:aevseev - openSUSE Build Service
[/QUOTE]
It seems home:gody and home:aevseev are the same user as the later matches the email address in the logs which you previously showed. However I still have no answer. I will try the second repo and see if the result is different.
BTW I now recall another discrepancy I found: the files /usr/sbin/bacula-* had owner root.root which I had to change to root.bacula to make it work as it was throwing a permission error in journal and couldn’t work at all.
Now in saying that, looking at the build log it does show some systemd warnings that should be fixed (well I would);
Welcome - openSUSE Build Service
I also note that have you started the relevant systemd services and checked the status?
Sure. FD (file daemon) and SD (storage daemon) work. But DIR (the Director) which rules them all cannot even start as I have pasted in a previous post.
If I had a way to test (I do have tape drives, but on sparc systems
) I could probably help more, but hopefully the maintainer/packager can assist better since I’m assuming they are using it…
Yes, I am looking forward to it.
[QUOTE=tsu2;2747425]The likely better way to discover dependencies and how to build is to follow the Bacula documentation.
Note that it’s a separate download from the main source files (you can get both at the following link)
Unfortunately, it looks like just unpacking and deploying the documentation is itself an exercise, after you unpack the documentation’s files, your first step should always be to read the README file and in this case it lists the documentation’s dependencies (latex2html, te_latex, tetex) and copy files to a running website (your choice. You can install and deploy an Apache website or I strongly recommend instead a nodejs or similar webserver if you know how. See my “How To” for installing nodejs at the end if you want to do this).
Not all, but most major projects nowadays have documentation even newbies might be able to follow.
TSU
[/QUOTE]
I know that but I haven’t gone into those complications as the documentation is available online anyway.
[QUOTE=arvidjaar;2747443]One solution is to change service to create PID file in subdirectory (like /run/bacula) and pre-create this subdirectory with correct permissions using either tmpfiles snippet or ExecStartPre in service.
[/QUOTE]
I have been thinking the same. However considering so many “hacks” need to be used as workarounds I am questioning the ease of maintenance of such system in the long term (considering that this path is also in the *.service files as well as in the *.conf ones). With Bacula 5.2.13 I never had these problems and there was no need for making things so very custom in every sense just to make the software work.
I do not know bacula internals, but usually you should always run your service with the least privileges possible. If this service does not need root, do not run it as root.
That’s what I thought. I really don’t know why it can’t start as user ‘bacula’ though. Is that something that needs to be fixed during compilation or ‘make install’?
I am going to make a few more tests before attempting to build the whole thing myself. But I am really trying to avoid making anything hard to maintain in the long term.