From: <to...@cu...> - 2005-01-06 15:10:46
|
Craig, I have assumed to date that there could only be one entry in the hosts file per client -- what you are proposing below would (I believe) require multiple entries in the hosts file? Thanks, Todd Message: 3 To: Michael Jeltsch <je...@cs...> cc: bac...@li... From: Craig Barratt <cba...@us...> Subject: Re: [BackupPC-users] One smb (win xp) client - multiple users: cgi-bin access only to own backups? Date: Tue, 04 Jan 2005 22:07:34 -0800 Michael Jeltsch writes: > We have a (standalone) Windows XP backuppc client with many users. The > Document folders of this client's users are at the moment backed as > individual directories using administrator access via smb. We want > every user to have access via the web interface to his own backups. > But using the current setup, every user must be specified in the hosts > file and thus has access to all folders (including the other users' > folders). How can I set up backuppc that each user of this client can > only see and restore his own backups? Unfortunately the user permissions only have the granularity of clients, so a user can access either an entire client or not at all. One solution is to create a client for every directory (or user). You might use client names like "HOST_USER", meaning that user's directory on that host. The per-client config.pl file would contain two important settings: # point at the real machine $Conf{ClientNameAlias} = 'REAL_HOST_NAME'; # backup just the directory for USER $Conf{BackupFilesOnly} = 'USER_PATH'; Each client will act like a different machine, so multiple backups might happen at the same time (but on different user directories of course). Then each client can just have permissions for that user. Craig |
From: Michael K. <Mic...@we...> - 2008-01-30 19:15:13
|
Craig Barratt <cbarratt <at> users.sourceforge.net> writes: > > todd <at> curryweb.com writes: > > > I have assumed to date that there could only be one entry in the hosts > > file per client -- what you are proposing below would (I believe) require > > multiple entries in the hosts file? > > That's right. From BackupPC's point of view these are different > clients, so each appears in the hosts file etc. But at the last > moment before doing the backup, $Conf{ClientNameAlias} redirects > to the real client. > > This same method can also be used to backup different parts of > the filesystem on a client with different frequencies and expiry > schedules. > > Craig > > ------------------------------------------------------- > The SF.Net email is sponsored by: Beat the post-holiday blues > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > _______________________________________________ > BackupPC-users mailing list > BackupPC-users <at> lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/backuppc-users > http://backuppc.sourceforge.net/ > > Hi list, since a while, I'm using the method Craig described before, and it's ok to set up for few PC's with few users. However, for PC's of group size (10-20 users), this becomes quite cumbersome. Moreover, the multiple entries for each PC bloat the list in the web interface. I would be happy if a host line could be of the following style: host dhcp adminUser1[,adminUser2...] user1[,user2...] The admin users would have admin rights, and the normal users would be able to operate on their files only. Is it a design feature of BackupPC which forbids implementation of such a functionality? Well, I already notice one problem to solve is what is about user files which are in a directory not owned by the user readable by a certain group but not world. Is the user part of this group? But, I believe this would be an improvement appreciated by many. Best regards, Michael |