nssbackup-team team mailing list archive

[robert leleu <question54062@xxxxxxxxxxxxxxxxxxxxx>]

Question #54062 on NSsbackup changed:
https://answers.edge.launchpad.net/nssbackup/+question/54062

robert leleu posted a new comment:
complementary informations/

Herbelow the log of the recent test made to see if any lockfile is made.
This log does not show the warning line

And at the time I find in /mnt  an empty nssbackup repertory created at
20:59 (and not a sbackup, as stated in the log), and an old empty
sbackup repertory, from dec 12 12:05, presumably from previous use of
sbackup....

Should I delete these before a new test?


NSSBackup 'Default Profile' Logger

==============

2008-12-14 20:59:23,168 - DEBUG - ConfigManager.py:validateConfigFileOpts(421) - Validating config file
2008-12-14 20:59:23,169 - INFO - ConfigManager.py:__init__(269) - ConfigManager created with '/etc/nssbackup.conf'
2008-12-14 20:59:23,170 - INFO - BackupManager.py:__init__(71) - Création du BackupManager 
2008-12-14 20:59:23,554 - INFO - BackupManager.py:makeBackup(90) - Début de la sauvegarde
2008-12-14 20:59:23,555 - DEBUG - BackupManager.py:__setlockfile(380) - Created lockfile at '/var/lock/sbackup.lock' with info '11509'
2008-12-14 20:59:23,556 - INFO - BackupManager.py:makeBackup(95) - Initialisation de FUSE FILE ACCESS MANAGER
2008-12-14 20:59:23,677 - INFO - BackupManager.py:__checkTarget(419) - Création du répertoire cible '/mnt/sbackup/ftp_tux@serveur/'

-- 
You received this question notification because you are a member of
NSsbackup team, which is an answer contact for NSsbackup.