Menu
▾
▴
Re: [BackupPC-users] unable to build backuppc from source
|
From: daggs <da...@gm...> - 2025-11-23 16:43:21
|
<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Greetings,</div> <div> <div> </div> <div>my apologies for top posting but I get the mail in html form and it doesn't work properly nor conversion to text.</div> <div>I'm using vm so no need for a docker container</div> <div> </div> <div>Thanks for the suggestion thought.</div> <div> </div> <div> </div> <div> <div name="quote" style="margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"> <div style="margin:0 0 10px 0;"><b>Sent:</b> Saturday, November 22, 2025 at 11:38 PM<br/> <b>From:</b> "Adam Goryachev via BackupPC-users" <bac...@li...><br/> <b>To:</b> "General list for user discussion, questions and support" <bac...@li...><br/> <b>Cc:</b> "Adam Goryachev" <mai...@we...><br/> <b>Subject:</b> Re: [BackupPC-users] unable to build backuppc from source</div> <div name="quoted-content"> <div>Jumping in late here...<br/> You might like to look at the BackupPC docker container, I recall it runs as non-root, and also will isolate itself from the rest of the os.<br/> If nothing else, it should have some helpful scripts, since also from memory,it is based on alpine linux....<br/> I've been running it that way on two servers for a year or so with no issues so far.<br/> <br/> Regards,<br/> Adam</div> <div class="gmail_quote"> <div>On 23 November 2025 3:57:49 am AEDT, "G.W. Haywood" <ba...@ju...> wrote:</div> <blockquote class="gmail_quote" style="margin: 0.0pt 0.0pt 0.0pt 0.8ex;border-left: 1.0px solid rgb(204,204,204);padding-left: 1.0ex;"> <pre class="k9mail"> </pre> <div>Hello again,<br/> <br/> On Sat, 22 Nov 2025, daggs wrote:</div> <blockquote class="gmail_quote" style="margin: 0.0pt 0.0pt 1.0ex 0.8ex;border-left: 1.0px solid rgb(114,159,207);padding-left: 1.0ex;"> <div>On Sun, 16 Nov 2025, G.W. Haywood wrote:</div> <blockquote class="gmail_quote" style="margin: 0.0pt 0.0pt 1.0ex 0.8ex;border-left: 1.0px solid rgb(173,127,168);padding-left: 1.0ex;"> <div>On Sun, 16 Nov 2025, daggs via BackupPC-users wrote:</div> <blockquote class="gmail_quote" style="margin: 0.0pt 0.0pt 1.0ex 0.8ex;border-left: 1.0px solid rgb(138,226,52);padding-left: 1.0ex;"> <blockquote class="gmail_quote" style="margin: 0.0pt 0.0pt 1.0ex 0.8ex;border-left: 1.0px solid rgb(252,175,62);padding-left: 1.0ex;"> <div>I'm working on building backuppc from source on alpine linux on the</div> </blockquote> <div>home folder of a user ...</div> </blockquote> <div>...<br/> I've just committed a change to makeDist which adds the '--verbose'<br/> option. If you grab the new version and run that with --verbose added<br/> to the command line you will probably see what's missing ...<br/> ...<br/> Please let me know how you get on. So far, you're doing famously!</div> </blockquote> <div><br/> With the new feature, I was able to compile it and install it on the<br/> home folder of the user I want to run it.</div> </blockquote> <div><br/> :)<br/> </div> <blockquote class="gmail_quote" style="margin: 0.0pt 0.0pt 1.0ex 0.8ex;border-left: 1.0px solid rgb(114,159,207);padding-left: 1.0ex;"> <div>two question if I may:</div> </blockquote> <div><br/> It's what we're here for.<br/> </div> <blockquote class="gmail_quote" style="margin: 0.0pt 0.0pt 1.0ex 0.8ex;border-left: 1.0px solid rgb(114,159,207);padding-left: 1.0ex;"> <div>1. Is there a way to run the perl configuration silently? so the<br/> installation can be automated?</div> </blockquote> <div><br/> Firstly I'm not sure that it's necessary for something to be silent<br/> just so that it can be automated. But secondly, yes, in fact several<br/> ways. The simplest is probably to send the output to the bit-bucket,<br/> or '/dev/null' as it's known in the Unix world. If, when you run a<br/> command in a shell script (or at the command prompt), you put at the<br/> end of the command line in the script (or the command at the prompt)<br/> the characters ' 1>/dev/null 2>&1' (excluding the quotes that I've<br/> used there) then the output from the script (or command) will be sent<br/> to a device whose only real job is to discard all its input. This is<br/> one example of what we call 'redirection'. In this case redirecting<br/> the standard output and standard error output 'streams'. Standard<br/> output is '1>' (for the 'bash' shell and some others, just '>' on its<br/> own means the same thing) and standard error is '2>'. The part that<br/> reads '2>&1' means "send the output from standard error to the same<br/> place that standard output will go".<br/> <br/> There are other ways to use redirection. You can send the output to a<br/> file (or files, for example '>./stdout.log 2>./stderr.log'). That's<br/> what I usually do if I don't want to see reams of verbose output on<br/> the screen, but I want to be able to look back later at what it said.<br/> <br/> You might remember that I suggested in an earlier mail that you could<br/> delete some text from the 'makeDist' script, to make its output more<br/> verbose. That was exactly the same thing in reverse. But I digress.<br/> </div> <blockquote class="gmail_quote" style="margin: 0.0pt 0.0pt 1.0ex 0.8ex;border-left: 1.0px solid rgb(114,159,207);padding-left: 1.0ex;"> <div>2. As I use alpine linux, I've opted not to use systemd, ...</div> </blockquote> <div><br/> I understand perfectly. ;)<br/> </div> <blockquote class="gmail_quote" style="margin: 0.0pt 0.0pt 1.0ex 0.8ex;border-left: 1.0px solid rgb(114,159,207);padding-left: 1.0ex;"> <div>which file from .../src/init.d should I select?</div> </blockquote> <div><br/> Using a search engine I searched for "alpine linux" "init scripts".<br/> Here are a few of pages that I found with a few clicks. I haven't<br/> spent a lot of time on them but they look to be useful documentation.<br/> <br/> <a href="https://wiki.alpinelinux.org/wiki/Writing_Init_Scripts" target="_blank">https://wiki.alpinelinux.org/wiki/Writing_Init_Scripts</a><br/> <a href="https://wiki.alpinelinux.org/wiki/OpenRC" target="_blank">https://wiki.alpinelinux.org/wiki/OpenRC</a><br/> <a href="https://github.com/OpenRC/openrc" target="_blank">https://github.com/OpenRC/openrc</a><br/> <br/> Typical startup/shutdown scripts will do things like checking that the<br/> resources which need to be available *are* available so that the thing<br/> which is being started can, when started, do its job. For BackupPC,<br/> for example, you'd normally expect at least all the filesystems to be<br/> accessible - so that BackupPC can find its configuration files, write<br/> backup data to the pool and so on - and the network to be functioning<br/> so it can fetch from other systems the data that you want to back up.<br/> The 'shutdown' part of the startup/shutdown scripts generally means a<br/> way of stopping the thing that was started in a 'graceful' way. Some<br/> processes are a little fussy about that, they may for example need to<br/> close files in a particular way or make sure that when the files are<br/> closed there's something written to the file which marks it as having<br/> been 'safely' closed, whatever 'safely' means. BackupPC isn't fussy.<br/> <br/> Because you're running BackupPC in a user home directory I'm guessing<br/> that things like that will already have been taken care of, so I'm not<br/> sure that any of the init-style scripts will be exactly what you want.<br/> Perhaps all you'd really need to do is type the command<br/> <br/> /path/to/your/BackupPC/bin/BackupPC -d<br/> <br/> or alternatively have a cron job check that BackupPC is running, and<br/> if it isn't, start it (using that same command). Once it's started,<br/> the BackupPC daemon will run until something stops it. Around here,<br/> it will typically run for many months at a time without interruption.<br/> <br/> Anyway after all that it seems to me after a quick look at the docs<br/> above that people have taken Gentoo scripts and used them as a basis<br/> for something on Alpine. That might be a good place to start as it's<br/> stuff you will probably want to be familiar with in future anyway. In<br/> addition to starting the BackupPC backup server itself you might also<br/> want the same script to start a Web server (probably Apache) or maybe<br/> at least check that it's running, and if not warn you. If BackupPC is<br/> configured to use an SCGI process as an intermediary between it and a<br/> Web server, it will start it (and stop it) itself.<br/> <br/> Note that although a full-bells-n-whistles BackupPC installation will<br/> run a Web server, BackupPC will run fine without one. It will still<br/> back things up. The Web server is primarily needed for point'n'shoot<br/> monitoring and control. After you start BackupPC you *can* control it<br/> and get information from it by sending messages to it from the command<br/> line. There are scripts in the archives of this Mailing List (also on<br/> the BackupPC Wiki) which show you how you can do that sort of thing.<br/> You might for example run a cron job which queries BackupPC each day -<br/> perhaps at a time when you expect all the backups to be finished - and<br/> sends you an email with the results.<br/> <br/> HTH<br/> </div> </blockquote> </div> _______________________________________________ BackupPC-users mailing list Bac...@li... List: <a href="https://lists.sourceforge.net/lists/listinfo/backuppc-users" target="_blank">https://lists.sourceforge.net/lists/listinfo/backuppc-users</a> Wiki: <a href="https://github.com/backuppc/backuppc/wiki" target="_blank">https://github.com/backuppc/backuppc/wiki</a> Project: <a href="https://backuppc.github.io/backuppc/" target="_blank">https://backuppc.github.io/backuppc/</a></div> </div> </div> </div></div></body></html> |
