search for: reallow

...le all IP addresses that failed SSH login more than X times and then executes a command such as shorewall drop <iplist> ; shorewall save (a logdigest-type variant aimed at shorewall''s dynamic functionalities). By the way, how does one "reset" the dynamic blacklist to "reallow" everyone without specifying IPs? (shorewall allow?) Thanks __________________________________ Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. http://promotions.yahoo.com/new_mail

Hmm, the danger in this is that duplicated factor levels _used_ to be allowed (i.e. multiple codes with the same level). Disallowing it is what broke read.spss() on some files, because SPSS's concept of value labels is not 1-to-1 with factors. Reallowing it with different semantics could be premature. I mean, if we hadn't had the "forbidden" step, read.spss() could have changed behaviour unnoticed. So what if there is code relying on duplicate factor levels, which hasn't been run for some time? -pd > On 23 Jun 2017, at 10:...

...6.2017 11:51, peter dalgaard wrote: > Hmm, the danger in this is that duplicated factor levels _used_ to be allowed (i.e. multiple codes with the same level). Disallowing it is what broke read.spss() on some files, because SPSS's concept of value labels is not 1-to-1 with factors. > > Reallowing it with different semantics could be premature. I mean, if we hadn't had the "forbidden" step, read.spss() could have changed behaviour unnoticed. So what if there is code relying on duplicate factor levels, which hasn't been run for some time? Indeed. The read.spss code now...

>>>>> Paul Johnson <pauljohn32 at gmail.com> >>>>> on Fri, 16 Jun 2017 11:02:34 -0500 writes: > On Fri, Jun 16, 2017 at 2:35 AM, Joris Meys <jorismeys at gmail.com> wrote: >> To extwnd on Martin 's explanation : >> >> In factor(), levels are the unique input values and labels the unique output >>