All,
I was a subscriber to this list, but I just can't handle the traffic
volume, so I'm not any more. However, the list has been a big help to
me, so I thought I might pass on something that I found when going
through an OSF/1 upgrade from 1.3 to 3.2.
I run Samba on a DEC 4000/300 serving a variety of clients including
Windows NT and Windows 3.1 with Pathworks 5.1. After the upgrade, the
Pathworks clients could no longer connect to the server. It turns out
that the Pathworks clients are a lot more sensitive than most other
clients, and the recompiled version of samba was passing them something
they couldn't handle. I found a patch for the code:
http://lake.canberra.edu.au/pub/samba/digest/401-500/0004.html
which fixed the problem. From the content of the fix it would appear that
malloc was behaving more like calloc (i.e. zeroing the data space
allocated) under the old OS, thereby masking the bug in samba (fixed in
v1.9.03) which caused problems for the pathworks clients.
For others performing similar OS upgrades, this change in the
behaviour of malloc might be something worth watching for.
Bill.
Received on Fri May 12 1995 - 11:16:19 NZST