On Wed, Aug 01, 2018 at 10:33:33AM -0500, Valeri Galtsev wrote:
>
> If you want to be rigorous with result (and I for one would), avoid locate:
> that one is using database which is updated how often? *hmm*, once a week.
Daily.
--
Normally the beautiful days in life come after fatigue and
Valeri Galtsev wrote:
> On 08/01/18 10:10, mark wrote:
>
>> This is among the things we need to do when a user leaves, and it's a
>> larger question than it sounds. Our Office has many servers, with a good
>> number of fileservers for projects, with large filesystems (i.e. 10's
>> of TB). Can
On 08/01/18 10:10, mark wrote:
This is among the things we need to do when a user leaves, and it's a
larger question than it sounds. Our Office has many servers, with a good
number of fileservers for projects, with large filesystems (i.e. 10's of
TB). Can anyone think of a way *other* than
On Wed, 1 Aug 2018, mark wrote:
This is among the things we need to do when a user leaves, and it's
a larger question than it sounds. Our Office has many servers, with
a good number of fileservers for projects, with large filesystems
(i.e. 10's of TB). Can anyone think of a way *other* than
This is among the things we need to do when a user leaves, and it's a
larger question than it sounds. Our Office has many servers, with a good
number of fileservers for projects, with large filesystems (i.e. 10's of
TB). Can anyone think of a way *other* than running what's probably a
many-hour
5 matches
Mail list logo