Am Freitag, 4. Dezember 2015 schrieb Gene Heskett:

> Tried that from an ssh -Y login to GO704 just now.
> 
> That claims that kmail is already running, which of course it is, 
> on /this/ machine, and while a root htop session on /sshnet/GO704 shows 
> akanadi etc running there, no kmail is showing.  Since it is this 
> machines kmail that handles the fetching and sorting to the proper 
> folders, this one should remain in operation to handle incoming mail. 
> Cannot each session of kmail on the remote machines maintain its own 
> read mail database, obviating any need for the remote session of kmail 
> to have write perms, with that potential for a clash between kmails 
> wrecking the whole party?
> 
> That means that I would have to do a session of mark all read to keep 
> those databases in sync if I am at one of the other 3 machines, as a way 
> to keep from having to read the whole, large fraction of a million 
> messages each time I ran kmail on the remote machine from its own 
> console.
> 
> Thanks Nic.
> 
> Cheers, Gene Heskett

Hi Gene!

There is a misunderstanding I think. I was assuming you use this scenario:

- you have a machine that fetches your mail. On that machine you do nothing, you are not logged in, kmail is not running. let's call it "remote"

- you sit in front of a second machine, where TDE is running, but not kmail. let's call it "here"

- you do "$ ssh -X gene@remote /opt/trinity/bin/kmail". kmail (running on "remote") sends the GUI over to  "here"

Nik


-- 
Please do not email me anything that you are not comfortable also sharing with the NSA.