Pbackup 3.1.9-1

[zigbert]

Version 3.0.0 is uploaded. See main post.

[GeoffS]

Sigmund
Haven't been here for a while but I've just had an unhappy experience with Pbackup. I hope this has not already been reported, I've searched and can't find anything.
My daily incremental backup includes my 'data disk' which is a vfat partition from Windows days. It is 4.9Gb. Quite by accident I discovered a directory and contents not being backed-up. The files in this directory are normally updated by a Windows XP program. As the files are only text files I made a small update to one from Puppy, at the next backup it got backed-up.
I know I should not be using a Windows program but I use it for making dvds of my photos and having only returned 3 weeks ago from visiting your part of the world I've a LOT of photos to work with and a familiar program is appreciated, I don't do this sort of thing very often.
Anyway, is there any reason you know of why Pbackup wouldn't pick up a Windows update? The change dates are quite OK. I'll post all the config files etc. if you need some more info.
Cheers
Geoff
PS I still like your Pbackup, I won't kick it too hard.

[zigbert]

Good to see you around

I know I should not be using a Windows program

Hello... If it's good, of course you should. We should always use what's best. That's why I use Puppy, but who knows tomorrow...

About your problem:
Could it so easy that the date-setting in windows differs from Puppy? Or do we have yet another issue because FAT and EXT uses different attributes, and therefor are hard to compare? In 'sync' these are more obvious, and it has got a option to eliminate the problem.

Could you experiment with 'find -ctime' to see if you can see if it detects date correct (-ctime is checked by 'backup' to see if it is newer than last backup). If you change a file in windows, and then goes to puppy to see if it was changed today...


Sigmund

[GeoffS]

Sigmund-
Yes, this IS one of those problems with Windows & Linux & date/times.
When Windows reports 'Date last Modified' is it using ctime or mtime?
When ROX reports 'Date Last Modified' is it using ctime or mtime?
I modified a file in Windows and the 'Date Last Modified' was correctly reported in Windows. I booted Puppy and ROX shows the 'Date Last Modified' as 10 hours into the FUTURE. Modify a file in Puppy and 'Date Last Modified' is correct in Puppy and (I think) in Windows. I haven't checked in Windows but I'm fairly certain I'd have noticed a discrepancy. As I do most of this in the late afternoon and evening a 10 hour discrepancy would be rather obvious.
mtime -1 finds the file that I modified in Windows
ctime -1 does NOT find the file I modified in Windows.
I'm finding this rather confusing
Does your script use mtime or ctime or both?
I can't think of any easy way to 'play' with this other than by booting Windows and then Puppy. Using VirtualBox or the network I'd not be sure which was doing the actual updating and be more confused than ever . Using the 2 systems I always think of something I should have checked AFTER I've changed systems
I'll keep thinking.
Cheers
Geoff

[zigbert]

Pbackup uses only -ctime, which seems to the wrong choice. -mtime returns status of inode, while -ctime return filestatus. I don't see any bad sides of changing to -mtime, but I have to do some testing before we get a bugfix release.

Thanks for bug-help.
Sigmund

[GeoffS]

Sigmund
Thanks for reply and 'work'
Don't know your code but would it be possible to use both. Make all tests in the form 'if (ctime > date OR mtime > date) then backup-the-file'?
It appears to me that if either has been changed there is good reason to backup the file, 'backup' can't know why they have changed.
May make the backup file a bit bigger however, to me, that is a 'good' fault.
Cheers
Geoff

[zigbert]

"everything is possible"

But I think we go for -mtime, as I can't see any trouble with it.

[zigbert]

Version 3.0.1

Changelog:
- Refined function to select files/dirs to include/exclude.
- Japanese translation. Thanks to Jimmy Lu (nyu).
- Changed 'find'-syntax from -ctime to -mtime. More compatible with other filesystems (thanks to Geoffs)
- External cron-editor is changed from gcrontab to Pschedule.
- Got rid of some messages to terminal when running quiet mode.
- Moved crond from /etc/rc.d/rc.local to $HOME/.xinitrc to coexist with Pscedule and Pdrive_deamon.
- Bugfix: Radiobutton to select 'schedule weekly' missed time in description.
- Bugfix: Be sure item in crontabs is owned by Pbackup before spesify schedule.
- Minor code cleanup.


Download from main post

Sigmund

[zigbert]

Version 3.0.2

Changelog
- Improved code for setting html-viewer (Thanks to Dougal)
- Moved translators and contributers to 'about'
- Autoselect button in dialogs.
- Pbackup enviroment variables is put first in /usr/local/pbackup.
- Crond is now autostarted from ~/Startup, instead of ~/.xinitrc.
- Bugfix: accept symlinks to dir for choosing temporary storage.
- Bugfix: remove item from 'save-from' doesn't accept spaces in filename.
- Bugfix: symlink to dir is not accepted by 'sync' function
- Bugfix: restore file from CD/DVD.
- Bugfix: resore all in backup.

Download from main post

Sigmund

[disciple]

Try running

Code: Select all

jwm -p

and you'll see an error generated because of the & in pbackup.desktop
It should really be replaced by

Code: Select all

&

, although it doesn't seem to actually break anything...

[zigbert]

Yes, I'm an idiot.

My /usr/share/applications/pbackup.desktop:

Code: Select all

[Desktop Entry]
Encoding=UTF-8
Name=Pbackup backup to CD/DVD/HD
Icon=mini-diskette.xpm
Comment=Pbackup backup to CD/DVD/HD
Exec=pbackup
Terminal=false
Type=Application
Categories=Archiving
GenericName=Pbackup 

[zigbert]

Version 3.0.3 is uploaded. See main post.

[disciple]

3.03 still has a "broken" .desktop file

[zigbert]

Can you please try to make the necessary mods and report back. I can't see what's wrong with mine.

Sigmund

[disciple]

Sorry for not being clear enough - what you posted is fine, but it doesn't match what is in the .pet - unless somehow I've got an old .pet labelled as 3.03

[disciple]

I just downloaded the .pet again, and it does have the wrong .desktop file.

For what it's worth, to make the one in the .pet work you can just make it read like:

Code: Select all

[Desktop Entry]
Encoding=UTF-8
Name=Pbackup Backup & Sync
Icon=mini-diskette.xpm
Comment=Pbackup Backup & Sync
Exec=pbackup
Terminal=false
Type=Application
Categories=Archiving
GenericName=Pbackup Backup & Sync

There's not really any need to replace the .pet, as it doesn't actually break anything, just jwm -p doesn't like it, so it is worth fixing in future releases. I guess possibly some other window manager would have a real problem, but I doubt it.

[zigbert]

Fixed!

Thanks you
Sigmund

[disciple]

Oops
I just realised that even though jwm -p gives an error with "&" but doesn't with "&", "&" works fine, but "&" is actually broken
With my version pmirror, which is after pbackup in the menu, doesn't show up, but when you click pbackup, it runs pmirror.
So your version is better. But this seems like a bug in JWM? I am running JWM 1.8, so I don't know if it is the same with 2.x

[zigbert]

I make it 'Backup and Sync'. Then we're safe.

[disciple]

What does it actually do in the way of synchronisation? The file you posted "backup to CD/DVD/HD" might be a more accurate description - and it is probably a little clearer for new users anyway.