@Frederic ROBIN:
Does your original problem still exists for you when using latest PPA version
(RC9)? I've fixed the issue you've described in the latest version.
--
Bug précisement à...
https://bugs.launchpad.net/bugs/526544
You received this bug notification because you are a member of
Thank you for reporting this issue.
Can you provide some more information how to trigger this bug?
What type of schedule did you choose? Simple or custom cron definition. What
did you define?
Do daily backups work for you?
Thanks.
** Changed in: nssbackup
Status: Fix Released =
I use a custom cron definition (i.e., the cron file is stored in
/etc/cron.d). I also tried the simple daily schedule; in this case, the
cron file is stored in /ect/cron.daily, but within 24 hours it never
performed the backup.
My workaround to the issue was to replace
Hi,
A few days ago I installed nssbackup and configured it the same way
sbackup was, but it seems that the scheduling part has no effect
---i.e., there's an nssbackup file in the /etc/cron.d directory, but no
backups are done. The only way to do a backup is to open NSsbackup-
Configuration (the
Oups, je m'était trompé de source (trop ancien)
Toujours dans 'ConfigManager.py', Il faut remplacer :
execline = if [ -x '+Util.getResource(nssbackup)+' ]; then
+Util.getResource(nssbackup)+; fi;
par:
execline = if [ -x '+Util.getResource(nssbackup)+/nssbackup' ]; then
Hi Frederic,
Thank you for taking the time reporting this bug.
Although I got an idea of the reported bug, can you post a summary of
the bug description in English please.
Thank you in advance.
Jean-Peer
--
Bug précisement à...
https://bugs.launchpad.net/bugs/526544
You received this bug
Oups (2)
Replace:
execline = if [ -x '+Util.getResource(nssbackup)+' ]; then
+Util.getResource(nssbackup)+; fi;
By:
execline = if [ -x '+Util.getResource(nssbackup)+/nssbackup' ]; then
+Util.getResource(nssbackup)+/nssbackup; fi;
--
Bug précisement à...
https://bugs.launchpad.net/bugs/526544
In (poor) english :
See in Ubuntu server 8.04Lts and 9.10.
There's a bug that affect the scheduler of nssbackup in 'ConfigManager.py'. In
the scheduler when you select 'Exactly at' and 'everyday', nssbackup will not
launch at scheduled time.
To correct that, you must replace in
Thank you so much for your translation and for your help on this project.
I will review the described issue and include a fix for it.
** Changed in: nssbackup
Importance: Undecided = High
** Changed in: nssbackup
Status: New = In Progress
** Changed in: nssbackup
Milestone: None =
9 matches
Mail list logo
