Puppy Linux Discussion Forum

How do I start Pupsave Backup from the shell?
Does it have parameters so I don't have to click on anything? I mean auto-magic compress as .gz? It's for my backup script.

The command that runs the program:

pupsave-backup

ty

HarveyH wrote: Mon Aug 05, 2024 11:53 am

How do I start Pupsave Backup from the shell?
Does it have parameters so I don't have to click on anything? I mean auto-magic compress as .gz? It's for my backup script.

You can run Pupsave Backup from the shell with /usr/sbin/pupsave-backup. For auto-magic compression as .gz, use /usr/sbin/pupsave-backup -c -g.

jelly767 wrote: Tue Aug 06, 2024 1:57 pm

You can run Pupsave Backup from the shell with /usr/sbin/pupsave-backup. For auto-magic compression as .gz, use /usr/sbin/pupsave-backup -c -g.

That still pops up the graphic interface

Kind of a "moot" question in my case.

I have a custom script that sequentially backs-up all 12 occupants of the kennels, one after the other, all at the same time. Upon completion, I get a "Success!" confirmation using gxmessage, telling me exactly how long the entire procedure took from start to finish, and the time & date on which the process was run.....

I'm a bit of an 'outlier' with a lot of Puppy stuff. GUI apps / utilities are provided for no end of things, yet I largely ignore them and script my own custom solutions instead....

I don't 'play the game', do I?

Mike.

so provide the script or a link to it please!

It sounds like what is being asked for in this topic.

@bigpup

No, what I was asking was how to make pupsave-backup do it's magic in a script.
This is what I have

#!/bin/sh
pupsave-backup -c -g
rsync -avu --exclude dpupbw64save --delete "/mnt/home/" "/mnt/sdb1/LinuxBackups/"
sync

It works fine, but I still have to click on the pupsave-backup GUI. I added the -c -g as suggested, but it doesn't do anything.

I'm excluding the pupsave folder itself because all I want are the archived backups and other stuff in /mnt/home. sdb1 is an NTFS partition and I don't want thousands of weird-ass named Linux files in there.

bigpup wrote: Thu Aug 08, 2024 4:57 pm

so provide the script or a link to it please!

It sounds like what is being asked for in this topic.

If I'd thought it was relevant, Bigs, I would have done......but since it's written to work ONLY for my specific set-up, it wouldn't do you any good if I did. I never put it together with 'publication' in mind, so it never got written in such a way that it COULD work for anyone else. In its present form, it's only good as a template to provide a 'starting-point' for others to modify.

Really, it was more of an observation than anything else.

You're very welcome to look at it if you want, but it would need quite a bit of work before it would function for anyone else. This copies entire 'frugal' installations across, NOT just the 'save'......but then I guess not too many Puppy users have got literally terabytes of spare, available storage space like I have. As it stands, it's written to run from inside a directory named, quite simply, "BACKUPS".

I'll attach it here, mate. Do with it what you like...

@HarveyH :-

See, this is WHY I "rolled my own".

Unless otherwise stated, you can generally assume that most native Puppy apps will offer a GUI of some kind. Now; due to the way a script needs to be written - in order to pass commands/arguments to a functional GUI - it's a bit more complicated to turn a GUI app into a non-GUI one than it at first appears. Like, there's more to it than simply 'commenting out' all references to the GUI.

I wanted a non-GUI way of performing an operation SPECIFIC to MY set-up.....with intermediate GTK-dialog banners for each stage....and a final 'message-window' giving me information that I wanted for my own benefit.

Sometimes, it's just quicker to write your own, starting from a blank page, than it is to try & modify someone else's work....

Mike.

Thanks @mikewalsh for sharing this.

I'm not very good at scripting, but I like seeing how people do it.
I keep trying to pick it up.
I like your simple approach.