All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Hirst <rhirst@linuxcare.com>
To: Joerg Hartmann <J.Hartmann@reinarts.de>
Cc: parisc-linux Mailinglist <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] can not get samba to work
Date: Wed, 19 Dec 2001 14:47:29 +0000	[thread overview]
Message-ID: <20011219144729.Y1897@linuxcare.com> (raw)
In-Reply-To: <881475869708.20011219132844@reinarts.de>; from J.Hartmann@reinarts.de on Wed, Dec 19, 2001 at 01:28:44PM +0100

On Wed, Dec 19, 2001 at 01:28:44PM +0100, Joerg Hartmann wrote:
> Hello parisc-linux users,
> 
> i can not get samba to work on my 720 with the 0.9.3 Debian.
> smbd dies immediatly with an error message in log.smbd:
> [2001/12/16 19:51:43, 0] lib/messages.c:message_init(97)
>   ERROR: Failed to initialise messages database

This looks like a glibc problem to me - I think it is calling fcntl
where it should be calling fcntl64, and using FSETLKW rather than
F_SETLKW64.

samba builds with

-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE

Using a test program, without those defines, i386 strace shows:

fcntl64(3, F_SETLKW, {type=F_WRLCK, whence=SEEK_SET, start=0, len=1}) = 0

with those defines:

fcntl64(3, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=0, len=1}, 0xbffffa9c) = 0


Now on hppa, without those defines

fcntl(3, F_SETLKW, {type=F_WRLCK, whence=SEEK_SET, start=0, len=1}) = 0

and with them:

fcntl(3, F_SETLKW, {type=F_WRLCK, whence=SEEK_SET, start=31, len=0}) = 0


note that 'start' and 'len' are wrong in the last case; I think that's
because glibc used a 64 bit struct flock, but didn't specify F_SETLKW64
(and didn't call fcntl64).

Richard

      reply	other threads:[~2001-12-19 14:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-19 12:28 [parisc-linux] can not get samba to work Joerg Hartmann
2001-12-19 14:47 ` Richard Hirst [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20011219144729.Y1897@linuxcare.com \
    --to=rhirst@linuxcare.com \
    --cc=J.Hartmann@reinarts.de \
    --cc=parisc-linux@lists.parisc-linux.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.