Hello Dirk, I have taken a look at what we might do in the core code to support some sort of on-line listing of the client files.
Currently the "estimate" command given either a Job name, or a Client+FileSet will produce a listing of all the files in the FileSet. This is useful for the user to know what is in his/her FileSet. Now in your case, I assume that you want to be able to get to the raw file structure on the Client machine, and it seems to me that if that is the case, you probably just need a simple directory listing routine. However, if you are eventually going to create FileSets and want to check them, then we probably should do the whole thing by having you pass some form of FileSet that would be compiled and sent to the client for listing. I can see several ways of doing this, and to decide, I think you need to tell me *exactly* what you are planning to do, then we can discuss it and see if the current FileSet interface will work or if we need to write a new filesystem listing routine. Best regards, Kern ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
