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
In case someone stumbles acr
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, also running Jessie, does have this pr
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.
>>
>> Interesting... Perhaps there are differe
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
On Tue, Nov 19, 2013 at 10:14:22AM +, Bernhard Schmidt wrote:
> 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
> W
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
6 matches
Mail list logo
