New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rear exits successufly when unknown backup method is specified #914
Comments
Technically it would be easy to let LogPrint "The BACKUP method ... with Error "The BACKUP method ... @schlomo @gdha In general I think rear should error out if mandatory In this particular case I think it is a good idea On the other hand I think all implemented BACKUP methods If someone implements a new BACKUP method I did a pull request: #916 Background information: In general you have zillions of possibilities In practice it is impossible to check all conditions In general you must carefully verify that your |
@jsmeix OK lets bail out when BACKUP method is not known - however, this means we should start with a developers guide, no? |
Yes! I initiated If you have time, just add what you like to have there |
Relax-and-Recover (rear) Issue Template
Please fill in the following items before submitting a new issue:
rear version (/usr/sbin/rear -V):
1.17.2 / Git
OS version (cat /etc/rear/os.conf or lsb_release -a):
RedHatEnterpriseServer 7
rear configuration files (cat /etc/rear/site.conf or cat /etc/rear/local.conf):
OUTPUT=USB
OUTPUT_URL="rsync://192.168.122.153/home/rear"
USB_DEVICE=/dev/sda1
GRUB_RESCUE=1
GRUB_PASSWORD=rootroot
BACKUP_URL=usr:///dev/sda1
BACKUP=HAHAHAHA
Brief description of the issue
rear mkbackuponly appears to work even though it doesn't create the backup (doesn't print any error and exits with exit code 0). In verbose mode It does prints a warning message, but it suggest it might still work:
The text was updated successfully, but these errors were encountered: