Samba Dropping Mounts - "Broken Pipe" msgs
auto852 at hushmail.com
auto852 at hushmail.com
Tue Sep 26 10:16:52 GMT 2000
At Mon, 25 Sep 2000 08:50:53 -0400, Bruce LaZerte <mail at fwr.on.ca> wrote:
>>>The "smb_retry: caught signal" problem should no longer occur in
>>>2.2.18pre3 or so. You will probably not find a RedHat rpm for kernel
>>>versions so you may have to compile your own.
>>Yikes, I've never compiled a kernel before and in this case (from what
>>could see) it requires compiling pre-patch-2.2.17-20 (required for)
>>pre-patch-2.2.18-10 (was the latest I could see) by someone named alan.
>>I've been a tech for over 6yrs and I've only just begun to learn linux.
>>(slap me silly). :)
>>Can those kernels be trusted? And any pointers towards information
>>I would go about compiling a new kernel without messing up my existing
>Having just got into this with Mandrake-lInux... I'll jump in here.
>First - downloading the latest kernel source 2.2.17, patching it to
>2.2.18-pre10 (or whatever) and recompiling is easy. I wouldn't do it
>production machine the first time, and I would have a good book to walk
>through it (or the kernel how-to - see Linux Documentation Project at
>www.kernel.org). But I didn't have any problems, and I've only been
>for a couple of weeks. The hardest part is figuring out which options/drivers
>to compile in or leave as modules. Your best guide is probably the
>configuration file from your original installation.
>Second - Getting Lilo to boot your new kernel is also simple, as is
>cp to a
>newly formatted floppy and booting from there.
>Third - But running the new kernel within your existing installation
>problems. I believe the RedHat install has around 40 different patches
>vanilla kernel. Some of these (e.g. the Alan Cox or AC patches) may
>in the newer version of the kernel and subsequent patch that you applied.
>may not. As a result, your installation may not work properly, although
>probably use it to test the new kernel funtionality and bug fixes.
>Fourth - Unfortunately, running the new kernel may screw up your original
>installation when you revert to the original kernel. It did in my case.
>I had a
>Mandrake 7.1 installation which has upwards of 170 patches on the 2.2.15
>kernel, bringing it to 2.2.15-4mdk. When I rebooted to the new patched
>I was missing supermount and some other functionality, but I could test
>smbfs was working. When I switched back to the original kernel, supermount
>still wasn't working properly. I may end up re-installing (not a big
>this is not a production machine).
>Fifth - it's a great learning experience <g>
Thanks Bruce, but yikes...it sounds to me like something I can't afford
to do at the moment. As I don't have a spare box to mess with and what I
am working with is a production server in a production environment what
am I to do? Risk it all (a secure gateway and firewall setup) in order to
"maybe" have Samba functionality? The system works great the way it is as
a secure firewall and gateway but to get samba to "Maybe" work sounds to
me like I might possibly have to re-install and redo the entire config just
for a possible "maybe" samba will work. Doesn't quite sound worth the time
nor the risk to me unless of course I was messing around..which is something
I cannot afford to do at this time.
.... Has anyone gotten Samba to work without any bugs whatsoever under Redhat
6.2 and Glftpd? What I need is stability, reliability, and no data corruption
or bad crc's etc etc.
I mean I could see what I can do about getting an extra machine together
just to tinker with but at this time it is not in my budget and I need to
know....is what I am attempting to accomplish -really- possible?
But thnx again Paul, and Urban for your help. I do very much appreciate
More information about the samba