search for: reoccurr

...-D_PATH_PRIVSEP_CHROOT_DIR=\"/var/empty/sshd\" -DSSH_RAND_HELPER=\"/usr/tgcware/libexec/ssh-rand-helper\" -DHAVE_CONFIG_H -c channels.c cfe: Warning 581: /usr/include/sys/param.h:223: Macro MAXPATHLEN redefined. cfe: Error: channels.c, line 2472: 'in_port_t' undefined; reoccurrences will not be reported. in_port_t *lport_p; ^ cfe: Error: channels.c, line 2546: 'lport_p' undefined; reoccurrences will not be reported. lport_p = &((struct sockaddr_in *)ai->ai_addr)-> ^ cfe: Error: channel...

I created a filter and verified it with fail2ban-regex against actual lines in my log and it works. During restarts of fail2ban, only some previous ip's get banned immediately whereas some need a reoccurrence despite the jail's config specification of maxretry and findtime suggesting the entries mandate blocking. I'd assume the behavior after a restart is noe way if it weren't for the seemingly random immediate notification of blocks being different? Anyone with experience using fail2b...

...us I was working with R --vsize 100 --nsize 1000000. Today when I tried to restart R I get the following error message: Error: a read error occured Fatal error: unable to restore saved data (remove .RData or increase memory) I increased memory up to --vsize 180 and --nsize 2000000, but the error reoccurrs. Is there a way to know whether this error results from a corrupt .Rdata or whether it is really a question of memory? And, are there good strategies for not loosing big .Rdata (except for backups between sessions and regular save.image() within sessions) ? That is, I guess, one of the few thing...

...d (Version 12.2(4)T7) and the problem disappeared. A Service-Policy had been applied to the outbound interface for QoS purposes. Removing the policy while a poor quality session was in progress had zero impact. Unfortunitly, no other Cisco data was gathered before the reboot. We're waiting for reoccurrence to gather additional doc. We are 100% confident this is a Cisco issue as opposed to * or any other resource. (Someone, maybe Eric, mentioned a Cisco QoS bug previously on this list. Indications are this might be the bug that person had mentioned.) The Cisco had been in use for a couple of ye...

...earing to come from a *@samba.org address. This will prevent situations such as occurred yesterday when an email worm forged a samba.org address (my own) and bounces began filtering back through the samba-announce list. We apologize for the noise and have hopefully addressed the issue to prevent a reoccurrence. cheers, jerry - --------------------------------------------------------------------- Alleviating the pain of Windows(tm) ------- http://www.samba.org GnuPG Key ----- http://www.plainjoe.org/gpg_public.asc "If we're adding to the noise, turn off this song"...

On 9/23/2016 3:02 PM, Jonathan Hunter via samba wrote: > Hi, > > On 23 September 2016 at 18:22, Rowland Penny via samba < > samba at lists.samba.org> wrote: > >> On Fri, 23 Sep 2016 18:12:32 +0100 >> Jonathan Hunter via samba <samba at lists.samba.org> wrote: >>> I can now successfully run "/usr/local/samba/sbin/samba_dnsupdate >>>

...of R 2.14.0, to be released on October 31: http://bit.ly/mVsg69 . R 2.13.2 was released on September 29: http://bit.ly/mRKVux The 2010 "Flash Crash" was the largest one-day stock market decline in history. An analysis in R of 24 billion trades investigates whether SEC rules to prevent a reoccurrence are effective: http://bit.ly/ohOv12 Nathan Yau of FlowingData mentions R in a post about "5 misconceptions about data visualization", and I take issue with charts that inject a political point of view (and not to mention chartjunk) into data visualizations:?http://bit.ly/oaSQQh Revo...

I have been trying to figure out this problem for a couple weeks no with no luck. Out of the blue, I started getting TSIG errors on my Samba AD DC. I pulled the logging extract below after turning up the log level to 10 and waiting for a reoccurrence. These errors will typically happen every few hours with one to three occurrences withing the same second. Can anybody tell from this what Samba is tripping over? I am running Samba v4.14.7 built from source on Rocky Linux release 8.8. If I run sudo samba_dnsupdate --verbose --use-samba-too...