It was a combination of having to use \ rather than / (As well as \\ on smbclient to check shares, and \\\\ for the network name prefix), as well as manually editing the windows security permissions on the folder to ensure the permissions were inherited by all children.
Also note that a windows account cannot be set to "Do not allow shell login" as it were, or /bin/null. No, you cannot stop an account actually logging in to windows itself and executing programs, not that I can find anyway. Silly if you ask me. That means with the password stored in plaintext in the backupPC config, someone need only compromise *that* and they can get full access to my system rather than just the backup shares. A situation I am not happy with and am searching for a solution for. +---------------------------------------------------------------------- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +---------------------------------------------------------------------- ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
