similar to: plot more plots from one matrix

Hello everybody. I have this object procedure property sensor_data sensor_date 1 S_10 nord 626821.0 2002-09-30T00:00:00+0200 2 S_10 nord 626821.0 2002-12-05T00:00:00+0100 3 S_10 nord 626821.1 2008-07-31T00:00:00+0200 4 S_1000 nord 626496.8 2002-09-30T00:00:00+0200 5 S_1000 nord 626496.8 2002-12-05T00:00:00+0100 6 S_1000

Hi, I have the following matrix (named m): key sensor_date Laser_1 Laser_2 Laser_3 2010-09-30T15:00:12+0200 6 3 1 2010-10-31T15:05:07+0100 5 4 2 2011-09-30T15:00:12+0200 6

2017-07-30T15:47:23.113000-04:00 www dovecot: pop3(facebook): Error: user facebook: Initialization failed: Namespace '': Mail storage autodetection failed with home=/home/facebook 2017-07-30T15:47:23.116805-04:00 www dovecot: pop3(facebook): Error: Invalid user settings. Refer to server log for more information. On 07/30/2017 03:42 PM, Ruben Safir wrote: > I've been running

I've been running dovecott without trouble for quite a why and now when I added a new user, it is not accepting the user and I can not track the problem. It says find more information in the server log, but it is not in /var/log/messages or /var/log/mail.err and nothing with lsof dovecot|grep log show anything to tail www:~ # dovecot -n # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux

Am 30.07.2017 um 21:49 schrieb Ruben Safir: > 2017-07-30T15:47:23.113000-04:00 www dovecot: pop3(facebook): Error: > user facebook: Initialization failed: Namespace '': Mail storage > autodetection failed with home=/home/facebook > 2017-07-30T15:47:23.116805-04:00 www dovecot: pop3(facebook): Error: > Invalid user settings. Refer to server log for more information. Define

This has been solved, as far as we can tell. Problem was with KillUserProcesses=1 in logind.conf. This has shown to kill mounts made using mount -a booth by root and by any user with sudo at session logout. Hope this will anybody else who run into this. Thanks 4 all your help and cheers Gabbe 1 juni 2017 kl. 09:24 skrev Gabriel Lindeborg <gabriel.lindeborg at

Hi folks, I expect that the response to this post will be "we don't need such a thing", but humour me for a moment by pretending that in fact we do. HTML5 added a number of new tags to the mix, but arguably the most significant is the `time` element. It associates a machine-readable timestamp with a human-readable string (e.g. `<time

On Thu, Jun 01, 2017 at 01:52:23PM +0000, Gabriel Lindeborg wrote: > This has been solved, as far as we can tell. > > Problem was with KillUserProcesses=1 in logind.conf. This has shown to > kill mounts made using mount -a booth by root and by any user with > sudo at session logout. Ah, yes, that could well be the cause of the problem. > Hope this will anybody else who run

All four clients did run 3.10.2 as well The volumes has been running fine until we upgraded to 3.10, when we hit some issues with port mismatches. We restarted all the volumes, the servers and the clients and now hit this issue. We?ve since backed up the files, remove the volumes, removed the bricks, removed gluster, installed glusterfs 3.7.20, created new volumes on new bricks, restored the

--- Daniel O'Connor <doconnor@gsoft.com.au> wrote: > Hi, > I work for a company which makes meteor and wind radar > (http://www.gsoft.com.au). > > On occasion (ie during meteor showers such as the Leonids) we > configure > the system to save raw data as it comes out of the acquisition > system, > the data rate for this varies (depends on acquisition parameters

Hi, I work for a company which makes meteor and wind radar (http://www.gsoft.com.au). On occasion (ie during meteor showers such as the Leonids) we configure the system to save raw data as it comes out of the acquisition system, the data rate for this varies (depends on acquisition parameters and number of coherent integrations etc), but usually it is around 600kb/sec. The data consists of 16