2008/7/29 Kevin Kubasik <[EMAIL PROTECTED]>:
[...]
>> * A gnome-do plugin would be good and a krunner plugin would be good. You
>> dont
>> really need to be at the hackfest to do these though :-)
>>
> Yeah, the more likely route would be to write an xesam plugin then use
> that to help troubleshoo
Follow-up and summary - it appears that beagle must check for a number of files
in ~/.beagle/config before overwriting/clearing the directory (please note -
this is an assumption only).
As it turns out I configured the indexing exclusion and copied daemon.xml,
indexing.xml and searching.xml i
> Unfortunately it looks like its 0.2.x and that's SLED10-SP2.
>
> Any idea why the files from /etc/skel are over written or deleted?
Nothing comes to my mind. Are you sure the location, name and the structure of
the file is correct ? I dont remember the details of the 0.2.x series but I
would s
Unfortunately it looks like its 0.2.x and that's SLED10-SP2.
Any idea why the files from /etc/skel are over written or deleted?
--
Craig Silva, IT Manager, ABX Logistics (Aust.) P/L
9 Trade Park Dve. Tullamarine. Melbourne. vic. 3043 Aus
> The problem now becomes how to exclude these directories from beagle
> indexing and to do it in a way that is automated by the system so that the
> exclusion is incorporated into the beagle config for each new user without
> some manual intervention by the user or admin.. The problem is that when
Dear beagle gurus,
we run SLED 10 and have multiple users logging into machines. We also have
drives mapped across the WAN that are mounted in the users home directory and
mounted via pam_mount because we have been reliant on AD for user
authentication.
We are moving to utilising the novell li
