backup-selection and information on last backups are now saved in user-specific file /home/userxy/.sepiola/config_appData . Reseller-information are still general thus not user-specific, so that all users will generally backup to the same server.
This modification applies also to scheduled backups. User must be logged in such that the correct selection is read from his home-directory.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If a cronjob / task has been scheduled by a certain user, it will run as this user even he isn't logged in. So it should not be necessary to be logged in interactively all the time as this user for being able to run the backup automatically, otherways there would be no guarantee that the backup will be done regularly or at system startup.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
also, when scheduling a cronjob, the displayed scheduled backup is the same for different users
backup-selection and information on last backups are now saved in user-specific file /home/userxy/.sepiola/config_appData . Reseller-information are still general thus not user-specific, so that all users will generally backup to the same server.
This modification applies also to scheduled backups. User must be logged in such that the correct selection is read from his home-directory.
If a cronjob / task has been scheduled by a certain user, it will run as this user even he isn't logged in. So it should not be necessary to be logged in interactively all the time as this user for being able to run the backup automatically, otherways there would be no guarantee that the backup will be done regularly or at system startup.
On all OS despite Windows Vista, it seems to work fine even if user isn't logged on. So please look at Windows Vista regarding this.