Pascal Hambourg wrote:
> Le 29/12/2017 à 18:27, Andrew W a écrit :
>>
>> On 27/12/2017 13:18, Bernhard Schmidt wrote:
>>> Current BIND9 defaults to doing DNSSEC verification. DNSSEC needs large
>>> packets. You might have an issue with UDP fragments being dropped
Andrew Wood wrote:
Hi,
> I have a server which acts as a DNS server for our LAN. All our internal
> servers have A records on it using a .local domain and it forwards all
> other requests out to the root servers using the in built list provided
> with BIND. All clients on the LAN have this ma
Daniel Pocock wrote:
Hi Daniel,
> My ISP is upgrading my connection to gigabit on Friday and I suspect my
> current router may struggle with it.
>
> My existing router runs OpenWRT but I've found the firewall and IPsec
> setup is a little bit constrained in that environment and it is tempting
>
Alan Chandler wrote:
Hi,
>>> Do you have /etc/hosts.allow / hosts.deny non-standard?
>>
>> Both appear empty (other than comments)
>
>
> So I added a line
>
> ALL: 127.0.0. 192.168.0.
>
> to /etc/hosts.allow
>
> and everything started working again
>
> Not sure if I need to include the 127.0.0 t
Bernhard Schmidt wrote:
> This is reproducible. To fix it it is enough to boot into the Wheezy
> kernel (even with init=/bin/sh), then reboot. It apparently does
> something to the root-fs (fsck?) which allows the Jessie kernel to boot.
Ben Hutchings had the right idea in B
Alan Chandler wrote:
Hi Alan,
> Today I am having database connection problems.
>
> Using mysql client to connect to my server "owl.home"
>
> mysql --host=owl.home --user=mythtv --password=XX mythconverg
> ERROR 2013 (HY000): Lost connection to MySQL server at 'reading
> authorization pac
Bernhard Schmidt wrote:
Hi,
>> Since I could not find anything secret in the initrd I have uploaded
>> both images
>>
>> http://users.birkenwald.de/~berni/volatile/783620_initrd_ok
>> http://users.birkenwald.de/~berni/volatile/783620_initrd_broken
>
> It is
Bernhard Schmidt wrote:
> Don Armstrong wrote:
>
> Hi Don,
>
>>> has anyone observed something similar to
>>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783620 on their
>>> Upgrade from Wheezy to Jessie? I'm still trying to figure out what'
Don Armstrong wrote:
Hi Don,
>> has anyone observed something similar to
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783620 on their
>> Upgrade from Wheezy to Jessie? I'm still trying to figure out what's
>> happening, and I don't really know where to look.
>>
>> I was unable to attach
Michael Biebl wrote:
Hi Michael,
>> has anyone observed something similar to
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D783620 on their
>> Upgrade from Wheezy to Jessie? I'm still trying to figure out what's
>> happening, and I don't really know where to look.
>>=20
>> I was unable t
Hi,
has anyone observed something similar to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783620 on their
Upgrade from Wheezy to Jessie? I'm still trying to figure out what's
happening, and I don't really know where to look.
I was unable to attach the screenshot so far (mail is accepted but
Bernhard Schmidt wrote:
Hi,
> Our TSM guy found the bugreport.
> http://www-01.ibm.com/support/docview.wss?uid=swg1IC92662&myns=apar&mynp=DO
>
> IC92662: TSM CLIENT CAN CRASH WITH CERTAIN NODENAMES ON LINUX
> DISTRIBUTIONS IF USING GLIBC 2.16 OR HIGHER IN THE FUTURE
I
Heya,
maybe someone has a great idea for this problem.
Citrix has released a new receiver (basically the client for their
terminalserver solution) for Linux.
http://www.citrix.com/downloads/citrix-receiver/linux/receiver-for-linux-130.html
The amd64 variant is basically i386 plus dependencies o
Bernhard Schmidt wrote:
Hi,
[ IBM TSM client segfaults on some Jessie boxes ]
>>>> The weird thing is, my colleague running sid on his desktop has the same
>>>> problem. My desktop, running Jessie, does _not_ have the same problem.
>>>> The VM in question,
Bernhard Schmidt wrote:
Hi,
>>> The weird thing is, my colleague running sid on his desktop has the same
>>> problem. My desktop, running Jessie, does _not_ have the same problem.
>>> The VM in question, also running Jessie, does have this problem.
>>
&g
Karl E. Jorgensen wrote:
Hi,
>> The weird thing is, my colleague running sid on his desktop has the same
>> problem. My desktop, running Jessie, does _not_ have the same problem.
>> The VM in question, also running Jessie, does have this problem.
>
> Interesting... Perhaps there are differences
Hi,
I'm a bit at a loss here, maybe someone has an idea how to look.
We run a commercial software called IBM Tivoli Storage Manager (TSM) for
Backup purposes. It is quite an ugly beast, but it works just fine on
Wheezy.
When upgrading to Jessie, it produces a segfault on most systems
root@lxmhs
Bernhard Schmidt wrote:
> I'm currently trying to streamline our Debian deployment using
> preseeding and I'm having issues setting a German keyboard layout. I use
> Wheezy daily 20121114 at the moment.
>
> Goals:
> - installer should be English
> - the count
Hi,
I'm currently trying to streamline our Debian deployment using
preseeding and I'm having issues setting a German keyboard layout. I use
Wheezy daily 20121114 at the moment.
Goals:
- installer should be English
- the country should be set to Germany (so timezone is okay)
- default locale of th
keith wrote:
> Bernhard Schmidt wrote:
>> The hard part seems to be matching the running kernel against the
>> version installed. I cannot figure out a good way so far. Nothing in the
>> running kernel seems to show the Debian version (i.e.
>> 2.6.32-41squeeze2), thus
Bob Proulx wrote:
>> The hard part seems to be matching the running kernel against the
>> version installed. I cannot figure out a good way so far. Nothing in the
>> running kernel seems to show the Debian version (i.e.
>> 2.6.32-41squeeze2), thus I cannot compare it. It is printed in the
>> boot
Hi,
the company I work for has a script on SLES/SuSE, that checks the
following three kernel versions
- latest version available in the repository
- version installed in /boot and thus likely to be loaded on next boot
- version running
and warns (and/or fixes) if there is a mismatch. I've been t
Andrei POPESCU wrote:
Hello,
>> I have not seen an explicit bug for it, but the 816 open bugs on
>> aptitude are somewhat hard to browse. Is this a known issue or
>> works-as-designed?
> I can only confirm your findings, still looking for a workaround.
I have reported bug #648313 for this.
htt
Hi,
I have a weird problem where my google foo is failing me (although I
guess it has been seen more than once before).
Long story short, I have a configuration management software (puppet)
that purges selective packages on each run (among others os-prober). It
is (by default) using apt for this
24 matches
Mail list logo
