search for: jedevnull

Can Samba 4.1.x be compiled fully static? On Wed, Feb 18, 2015 at 3:43 AM, Peter Serbe <peter at serbe.ch> wrote: > Jed Evnull schrieb am 17.02.2015 23:14: > > [Static cross-compile of Samba] > > The static 3.2.15 works fine on the pi, but fails under android since it > > can't find user root or guest. But that's another issue, I don't expect > any >

Can all of the compiled-in filepaths below be overrdden in smb.conf? I can't find documentation for the required smb.conf equivilents. If someone could supply them or post a link, I'd be very greatful. SBINDIR BINDIR SWATDIR CONFIGFILE LOGFILEBASE LMHOSTSFILE LIBDIR LOCKDIR PIDDIR SMB_PASSWD_FILE PRIVATE_DIR

I'm compiling samba-3.6.22 for android with the sourcery arm-2010q1 compiler. The compile itself goes fine, but when I copy smbd to my device it's not recognized as a binary. I get the error sh: ./smbd: No such file or directory file under linux tells me: smbd: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.16, not

Grr why is this so hard? Compiling samba-3.6.24 for android using the sourcery toolchain. Dropbear and busybox went w/o a hitch. I've googled the hell out of this, nothing I've found has helped. Here's my config: ./configure --without-krb5 \ --without-ldap \ --without-ads \ --disable-cups \ --enable-swat=no \ --enable-static=yes \ --disable-shared \ --with-winbind=no \

I recently compiled samba-3.2.15 for a Raspberry Pi V2 and while it seems to be working fine, when I ps aux | grep smbd I'm shown two or three successively numbered smbd jobs. The smbd log isn't showing anything weird, what's up with this?

I have an odd situation: nmbd will not start. This is samba 3.6.24, freshly compiled, running on a Raspberry Pi V2, 1Gb ram, quad-core, etc. smbd starts, and I can connect to the server my Mac and from an Android device, haven't tested Windows. ./nmbd -D does not start nmbd. I've tried starting ./nmbd -i -d10 to no effect, it returns immediately to the console, no hang or stall. No

I'm getting error messages when a connection is attempted: smbd/service.c:make_connection_snum(633) '[original location]/var/tmp' does not exist or is not a directory, when connecting to [IPC$] The original binaries have been moved to a new directory. The locations for : pid directory log file smb passwd file private dir lock dir have been specified in smb.conf. What can I do

As I said, the original binaries. I need to know if I can override this error with a smb.conf directory directive, just as you can override other compiled-in directories. On Fri, Feb 27, 2015 at 11:28 AM, Marc Muehlfeld <mmuehlfeld at samba.org> wrote: > Hallo Jed, > > Am 27.02.2015 um 17:06 schrieb Jed Evnull: > > I'm getting error messages when a connection is

Grr why is this so hard? Compiling samba-3.6.24 for android using the sourcery toolchain. Dropbear and busybox went w/o a hitch. I've googled the hell out of this, nothing I've found has helped. Here's my config: ./configure --without-krb5 \ --without-ldap \ --without-ads \ --disable-cups \ --enable-swat=no \ --enable-static=yes \ --disable-shared \ --with-winbind=no \

> > > From: Rowland Penny <rowlandpenny at googlemail.com> > To: samba at lists.samba.org > Cc: > Date: Tue, 17 Feb 2015 09:29:18 +0000 > Subject: Re: [Samba] ps aux | grep smbd > On 17/02/15 05:14, Jed Evnull wrote: > >> I recently compiled samba-3.2.15 for a Raspberry Pi V2 and while it seems >> to be working fine, when I ps aux | grep smbd I'm