On 10/22/2016 02:39 PM, bruce wrote:
On Sat, Oct 22, 2016 at 4:00 PM, jd1008 wrote:
On 10/22/2016 12:14 PM, Gordon Messmer wrote:
On 10/22/2016 06:13 AM, bruce wrote:
I've thought of having a "pid" file on the nfs, where each clientApp
would reset/lock/use the pidFile to
On 22/10/16 14:04, Samuel Sieb wrote:
On 10/21/2016 06:16 PM, Stephen Morris wrote:
Thanks Sam, I think I have that package installed so I'll have to find
where it installed the plugin to configure Firefox to use it as I'm
using the nightly version of upstream Firefox which at the moment is
On 22/10/16 14:04, Samuel Sieb wrote:
On 10/21/2016 06:16 PM, Stephen Morris wrote:
Thanks Sam, I think I have that package installed so I'll have to find
where it installed the plugin to configure Firefox to use it as I'm
using the nightly version of upstream Firefox which at the moment is
On Mon, 10 Oct 2016 10:35:01 -0700, stan wrote:
> > After last update of Claws-Mail reading new mails, something is
> > changed. I read first mail, after reading I move it into trash,
> > cursor jumps to last unread mail. Before update worked, after moved
> > trash, cursor went next unread mail.
On Sat, Oct 22, 2016 at 4:00 PM, jd1008 wrote:
>
>
> On 10/22/2016 12:14 PM, Gordon Messmer wrote:
>>
>> On 10/22/2016 06:13 AM, bruce wrote:
>>
>>> I've thought of having a "pid" file on the nfs, where each clientApp
>>> would reset/lock/use the pidFile to then get/use/delete
On 10/22/2016 12:14 PM, Gordon Messmer wrote:
On 10/22/2016 06:13 AM, bruce wrote:
I've thought of having a "pid" file on the nfs, where each clientApp
would reset/lock/use the pidFile to then get/use/delete the file as
required, but this seems tb slow.. but doable.
Probably. You'd have a
Could anyone knowledgeable be so kind as to inform me of the current status of
389's REST API?
1. Is it functional, stable ?
2. What can be done with it currently?
3. To what extent does the 389 server need to be configured before the REST API
can be utilized?
On 10/22/2016 06:13 AM, bruce wrote:
The idea, is that a clientApp, on a given clientVM will access a file
on the nfs, and then the nfs file is no long used.
It's difficult to offer performance tuning advice without more
information about what the app is doing, exactly. Is it reading it into
Hey List.
This is off topic, but I noticed the list has been quiet!!
Trying to get different thoughts on how to approach an issue.
I've got a situation, where I'm going to have a shared nfs, with a
bunch of files..
I'm going to have multiple client boxes/(vms) with each client,
running apps