You are not logged in.

#1 2010-01-15 09:57:32

Harey
Member
From: Bavaria, Germany
Registered: 2007-03-24
Posts: 359

[SOLVED] Samba 3.4.4 new dependency?

the update to samba 3.4.4 seems to introduce a new dependency. After the update the service wouldn't restart on my server because of a missing shared library libdm.so.0 which belongs to package dmapi. Installing this package (and a reboot) fixed the problem. I suggest correcting the PKGBUILD.

Hope this helps
Harvey

Last edited by Harey (2010-01-15 16:14:34)


Linux is like a wigwam: No Gates, no Windows and an Apache inside

Offline

#2 2010-01-15 10:32:48

wonder
Developer
From: Bucharest, Romania
Registered: 2006-07-05
Posts: 5,941
Website

Re: [SOLVED] Samba 3.4.4 new dependency?

i suggest to proper  report  on http://bugs.archlinux.org and specify architecture too

p.s only i686 related.

Last edited by wonder (2010-01-15 10:42:32)


Give what you have. To someone, it may be better than you dare to think.

Offline

#3 2010-01-15 12:21:44

Harey
Member
From: Bavaria, Germany
Registered: 2007-03-24
Posts: 359

Re: [SOLVED] Samba 3.4.4 new dependency?

wonder,

wonder wrote:

i suggest to proper  report  on http://bugs.archlinux.org and specify architecture too

I did not find anything in the forums about this. Of Course I would file a bug report, but before doing so there should be someone confirming the bug to prove that I am not wrong. This would avoid to waste the developer's precious time smile

wonder wrote:

p.s only i686 related.

Does this mean that you are affected by this too?

Harvey

Last edited by Harey (2010-01-15 12:22:33)


Linux is like a wigwam: No Gates, no Windows and an Apache inside

Offline

#4 2010-01-15 12:38:56

wonder
Developer
From: Bucharest, Romania
Registered: 2006-07-05
Posts: 5,941
Website

Re: [SOLVED] Samba 3.4.4 new dependency?

Harey wrote:
wonder wrote:

p.s only i686 related.

Does this mean that you are affected by this too?

i have x86_64 and i'm not affected

Last edited by wonder (2010-01-15 12:39:09)


Give what you have. To someone, it may be better than you dare to think.

Offline

#5 2010-01-15 13:19:59

Harey
Member
From: Bavaria, Germany
Registered: 2007-03-24
Posts: 359

Re: [SOLVED] Samba 3.4.4 new dependency?

wonder,

wonder wrote:

i have x86_64 and i'm not affected

This made me curious smile

Ok, I tried a box with x86_64 and... nothing. Another 32 bit box - same error. Ok, convinced, this is a bug big_smile


Harvey
(filing a bug report right now)
See:
http://bugs.archlinux.org/task/17851

Last edited by Harey (2010-01-15 15:10:47)


Linux is like a wigwam: No Gates, no Windows and an Apache inside

Offline

#6 2010-01-15 13:23:04

firecat53
Member
From: Lake Stevens, WA, USA
Registered: 2007-05-14
Posts: 1,542
Website

Re: [SOLVED] Samba 3.4.4 new dependency?

Thanks for the quick noticing! Bit me this morning too. Dmapi solved it -- didn't need the reboot, though smile

Scott

Offline

#7 2010-01-15 13:37:50

Harey
Member
From: Bavaria, Germany
Registered: 2007-03-24
Posts: 359

Re: [SOLVED] Samba 3.4.4 new dependency?

Scott,

firecat53 wrote:

didn't need the reboot, though smile

further investigation: Only smbd won't start because of the missing lib, winbindd and nmbd are starting. So calling /etc/rc.d/samba start will fail because of the two daemons running while /etc/rc.d/samba restart will work. Indeed, the reboot was not necessary.

My fault wink

Harvey


Linux is like a wigwam: No Gates, no Windows and an Apache inside

Offline

#8 2010-01-16 02:03:41

mdawgmike
Member
Registered: 2010-01-16
Posts: 2

Re: [SOLVED] Samba 3.4.4 new dependency?

I've been having troubles with Samba as well.  I am running x86_64. so it's either there's issues with that architecture too or it's something wrong with my setup.  The problem started when I did a pacman -Syu to get Apache working.  Basically, I rebooted my system and the daemon failed to load after that point.  Doing /etc/rc.d/samba start/stop/restart would result in a [FAIL] dialog coming up.  I tried re-installing both samba and gamin with no avail.  After seeing this post I installed dmapi, which has made it so samba can at least start again.

The problem now is that my shares still are not showing up on the network.  So...it's still effectively not working on my system.  Here's my /etc/samba/smb.conf...if it helps any (I redid it from scratch as a trouble shooting step and forgot to backup the old one, so I may have possibly not set something right.):

# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options (perhaps too
# many!) most of which are not shown in this example
#
# For a step to step guide on installing, configuring and using samba,
# read the Samba-HOWTO-Collection. This may be obtained from:
http://www.samba.org/samba/docs/Samba-H … ection.pdf
#
# Many working examples of smb.conf files can be found in the
# Samba-Guide which is generated daily and can be downloaded from:
http://www.samba.org/samba/docs/Samba-Guide.pdf
#
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
#
# NOTE: Whenever you modify this file you should run the command "testparm"
# to check that you have not made any basic syntactic errors.
#
#======================= Global Settings =====================================
[global]

# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
   workgroup = WORKGROUP

# server string is the equivalent of the NT Description field
   server string = Shorty

# Security mode. Defines in which mode Samba will operate. Possible
# values are share, user, server, domain and ads. Most people will want
# user level security. See the Samba-HOWTO-Collection for details.
   security = share

# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
;   hosts allow = 192.168.1. 192.168.2. 127.

# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
   load printers = no

# you may wish to override the location of the printcap file
;   printcap name = /etc/printcap

# on SystemV system setting printcap name to lpstat should allow
# you to automatically obtain a printer list from the SystemV spool
# system
;   printcap name = lpstat

# It should not be necessary to specify the print system type unless
# it is non-standard. Currently supported print systems include:
# bsd, cups, sysv, plp, lprng, aix, hpux, qnx
;   printing = cups

# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
guest account = mdawgmike

# this tells Samba to use a separate log file for each machine
# that connects
   log file = /var/log/samba/%m.log

# Put a capping on the size of the log files (in Kb).
   max log size = 50

# Use password server option only with security = server
# The argument list may include:
#   password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
# or to auto-locate the domain controller/s
#   password server = *
;   password server = <NT-Server-Name>

# Use the realm option only with security = ads
# Specifies the Active Directory realm the host is part of
;   realm = MY_REALM

# Backend to store user information in. New installations should
# use either tdbsam or ldapsam. smbpasswd is available for backwards
# compatibility. tdbsam requires no further configuration.
;   passdb backend = tdbsam

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting.
# Note: Consider carefully the location in the configuration file of
#       this line.  The included file is read at that point.
;   include = /usr/local/samba/lib/smb.conf.%m

# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
interfaces = lo eth0
bind interfaces only = true

# Browser Control Options:
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
;   local master = no

# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
;   os level = 33

# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
;   domain master = yes

# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
;   preferred master = yes

# Enable this if you want Samba to be a domain logon server for
# Windows95 workstations.
;   domain logons = yes

# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
;   logon script = %m.bat
# run a specific logon batch file per username
;   logon script = %U.bat

# Where to store roving profiles (only for Win95 and WinNT)
#        %L substitutes for this servers netbios name, %U is username
#        You must uncomment the [Profiles] share below
;   logon path = \\%L\Profiles\%U

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
;   wins support = yes

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
#       Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
;   wins server = w.x.y.z

# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one  WINS Server on the network. The default is NO.
;   wins proxy = yes

# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The default is NO.
   dns proxy = no

# These scripts are used on a domain controller or stand-alone
# machine to add or delete corresponding unix accounts
;  add user script = /usr/sbin/useradd %u
;  add group script = /usr/sbin/groupadd %g
;  add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
;  delete user script = /usr/sbin/userdel %u
;  delete user from group script = /usr/sbin/deluser %u %g
;  delete group script = /usr/sbin/groupdel %g


#============================ Share Definitions ==============================
[Shared]
        path = /home/mdawgmike/public_html
        available = yes
        browsable = yes
        public = yes
        writable = yes

;[homes]
;   comment = Home Directories
;   browseable = no
;   writable = yes

# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
;   comment = Network Logon Service
;   path = /usr/local/samba/lib/netlogon
;   guest ok = yes
;   writable = no
;   share modes = no


# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
;    path = /usr/local/samba/profiles
;    browseable = no
;    guest ok = yes


# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
[printers]
   comment = All Printers
   path = /var/spool/samba
   browseable = no
# Set public = yes to allow user 'guest account' to print
   guest ok = no
   writable = no
   printable = yes

# This one is useful for people to share files
;[tmp]
;   comment = Temporary file space
;   path = /tmp
;   read only = no
;   public = yes

# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
;   comment = Public Stuff
;   path = /home/samba
;   public = yes
;   writable = no
;   printable = no
;   write list = @staff

# Other examples.
#
# A private printer, usable only by fred. Spool data will be placed in fred's
# home directory. Note that fred must have write access to the spool directory,
# wherever it is.
;[fredsprn]
;   comment = Fred's Printer
;   valid users = fred
;   path = /homes/fred
;   printer = freds_printer
;   public = no
;   writable = no
;   printable = yes

# A private directory, usable only by fred. Note that fred requires write
# access to the directory.
;[fredsdir]
;   comment = Fred's Service
;   path = /usr/somewhere/private
;   valid users = fred
;   public = no
;   writable = yes
;   printable = no

# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %U option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
;  comment = PC Directories
;  path = /usr/pc/%m
;  public = no
;  writable = yes

# A publicly accessible directory, read/write to all users. Note that all files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of course
# be specified, in which case all files would be owned by that user instead.
;[public]
;   path = /usr/somewhere/else/public
;   public = yes
;   only guest = yes
;   writable = yes
;   printable = no

# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
;[myshare]
;   comment = Mary's and Fred's stuff
;   path = /usr/somewhere/shared
;   valid users = mary fred
;   public = no
;   writable = yes
;   printable = no
;   create mask = 0765

Last edited by mdawgmike (2010-01-16 02:12:26)

Offline

#9 2010-01-16 12:16:05

Harey
Member
From: Bavaria, Germany
Registered: 2007-03-24
Posts: 359

Re: [SOLVED] Samba 3.4.4 new dependency?

mdawgmike,

troubleshooting samba is tricky sad

Most of the smb.conf you posted is a comment. The lines with a '#' and a ';' are no working options but comments. This makes it hard to see the 'real' options.

I suggest starting with a clean smb.conf and following the wiki:
http://wiki.archlinux.org/index.php/Samba

I would use swat's wizards for an initial setup. And don't forget to put your user in the samba user db.

Harvey


Linux is like a wigwam: No Gates, no Windows and an Apache inside

Offline

Board footer

Powered by FluxBB