Displaying 5 results from an estimated 5 matches for "fixxes".
Did you mean:
fixes
2008 Feb 28
0
problem with the ltm package - 3PL model
Hi Xavier,
the reason you observe this feature is that in the 'constraint'
argument you should specify the values under the additive
parameterization, i.e., when in the second column of the matrix
supplied in 'constraint' you specify 2, then you need to provide the
easiness parameters (not the difficulty parameters) in the third
column. Check the Details section of ?tpm() and
2002 Jul 14
0
[Bug 348] infinite loop scanning wtmpx
http://bugzilla.mindrot.org/show_bug.cgi?id=348
tim at multitalents.net changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From tim at multitalents.net 2002-07-15
2015 Dec 10
1
CentOS 7, NetworkMangler, and ipv6
Yamaban wrote:
> On Thu, 10 Dec 2015 16:00, m.roth at ... wrote:
>
>> We've started having a problem with a CentOS 7 server. It looses its
>> IPv6 address, if I understand this issue correctly. We can get in,
>> if we do ssh -4, though.
>>
>> In the logs, I'm seeing this about twice an hour:
>> <warn> (pid 98466) unhandled DHCP event for
2004 Feb 03
0
RedHat 9 & VSFTPD & Digium Hardware Oddoties
Here is my experience so far to treat some issues I have been having with
Digium hardware (t100p, and x100p's.) I am not 100% certain these are
fixxes, but just something for people to try if they are expierencing
issues with the hardware performing quirky.
1st) Do NOT use Promise Array ATA Raid controllers in a sytem with Digium
Hardware. This created many random red alarm issues with the X100P card,
as I would see an error generated by both...
2015 Dec 10
6
CentOS 7, NetworkMangler, and ipv6
We've started having a problem with a CentOS 7 server. It looses its IPv6
address, if I understand this issue correctly. We can get in, if we do ssh
-4, though.
In the logs, I'm seeing this about twice an hour:
<warn> (pid 98466) unhandled DHCP event for interface ens3f0
Now, in googling, I get very few hits putting quotes around "unhanded dhcp
exception" - in fact, the