Mailinglist Archive: opensuse-security (757 mails)

< Previous Next >
Re: [suse-security] kernel panic under high load
  • From: Christoph Egger <egger@xxxxxxxxxxxxxx>
  • Date: Thu, 3 Jan 2002 15:58:22 +0100
  • Message-id: <20020103145644.10C2AE654C@xxxxxxxxxxxx>
On Thursday, 3. January 2002 11:00, lv426@xxxxxxxxxxxxxxx wrote:
> Kurt Seifried wrote:
> > simply download samba source rpm, samba tarball, edit samba spec file,
> > copy in tarball, voila. rpm makes it easy to build your own upgrade
> > packages.
> >
> >
> > Kurt Seifried, kurt@xxxxxxxxxxxx
> > A15B BEE5 B391 B9AD B0EF
> > AEB0 AD63 0B4E AD56 E574
> > http://www.seifried.org/security/
> >
> >
> > ----- Original Message -----
> > From: "Christoph Egger" <egger@xxxxxxxxxxxxxx>
> > To: <suse-security@xxxxxxxx>
> > Sent: Wednesday, January 02, 2002 6:19 AM
> > Subject: [suse-security] kernel panic under high load
> >
> >>Hello!
> >>
> >>I use SuSE 7.3 on a file server with Samba 2.2.1a (shipped with SuSE
> >> 7.3). But under high load, the SuSE Kernel panics.
> >>
> >>I am now downloading kernel 2.4.17 to compile and install myself.
> >>
> >>And I want to update Samba to 2.2.2, because of some oplock fixes.
> >>Is a ready SuSE rpm somewhere available?
> >>If not, which configure options have I to use in order to overwrite the
> >
> > old
> >
> >>binaries and that the binaries searches smb.conf in /etc/samba?
> >>
> >>--
> >>CU,
> >>Christoph
>
> Hi Christoph,
>
> this should do:
> <--snap
>
> ./configure --prefix=/usr/lib/samba --bindir=/usr/bin --sbindir=/usr/sbin
> --libdir=/usr/lib/samba
> --sysconfdir=/etc/samba --mandir=/usr/share/man
> --with-privatedir=/etc/samba --with-lockdir=/var/lock/samba
> --with-configdir=/etc/samba --with-swatdir=/usr/lib/samba/swat
> --with-smbwrapper
> --with-dce-dfs --with-automount --with-smbmount --with-msdfs
> --with-libsmbclient --with-acl-support --with-winbind --with-vfs
> --with-quotas
>
> snap --->

TNX, a lot! The fileserver runs very well now!
Kernel 2.4.17 + Samba 2.2.2 is a very stable combination!

I stresstested it by coyping and moving lots of data around (about 30 GB) and
the server runs and runs and runs... :)

Another problem: NFS! When I try to mount a directory via nfs, the fileserver
prints in /var/log/messages:
----------------------------------------
Jan 3 13:59:45 fileserver mountd[18775]: NFS mount of /home/install
attempted from 192.168.2.91
Jan 3 13:59:45 fileserver mountd[18775]: /home/install has been mounted by
192.168.2.91

on the client side, the mount command needs a loooong time to exit. When I
make a "ps axf | grep mount", then I get:
------------------------------------------
1911 pts/5 D 0:00 \_ mount -t nfs 192.168.2.70:/public/install
./install

Does anyone know, what goes wrong?


--
CU,
Christoph

< Previous Next >
Follow Ups
References