On Fri, 2007-07-06 at 12:45 +0530, Debajyoti Bera wrote: > > 1) Start beagled with "--networked" on machine-A So one does this as one's own uid on the remote machine? Presumably that beagled then indexes one's own ~ on the networked machine? Into a ~/.beagle/ dir? What are the thoughts of a single beagled run as root that works on behalf of all of the users on that machine? I'm thinking of a NASish type machine that hosts homedirs for example but does not really facilitate the users logging into it. This same beagled should be configurable to index other locations on the machine for "public access". The alternative of course is some form of "getent passwd | while read name; do su - name -c beagled --networked; done" but that starts a potentially large number of beagled processes. > 2) On machine-B, use "beagle-config networking AddNeighborhoodBeagleNode > hostname:portnumber" to add the machine-A (use portnumber = 4000) How about SD/rendezvous (or whatever it's being called these days) so that beagle automatically finds all of the networked beagleds on the network? > 3) On machine-B, run "beagle-query --local no --remote yes <search_terms>" to > search remote beagle. Is it intentional that the user has to know he is querying networked beagleds? Ideally this whole networked concept is hidden from the user, yes? > 4) Cross your fingers and hope the roof does not crash. The best part! :-) b. -- My other computer is your Microsoft Windows server. Brian J. Murrell
Attachment:
signature.asc
Description: This is a digitally signed message part