Bad file descriptors with samba-2.2.x -- more details.
wolfgang.glas at ev-i.at
wolfgang.glas at ev-i.at
Fri Jun 28 06:59:01 GMT 2002
Dear samba team,
Here is an exact description on how to reproduce the bad file decsriptor
error using a trivial smb.conf.
My configuration is smaba-2.2.5 under Linux (SuSE-80; kernel 2.4.18)
One host has all filesystems on reiserfs on top of LVM.
The other host is ext3-based with /usr and the root filesystem running
reiserfs.
(/ext and /home are on ext3)
The smb.conf file follows:
----------------------------------------
# Samba config file created using SWAT
# from localhost (127.0.0.1)
# Date: 2002/06/28 10:19:30
# Global parameters
[global]
workgroup = abc
server string = Samba %v on my_host
encrypt passwords = Yes
map to guest = Bad Password
socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY
character set = ISO8859-15
os level = 2
printing = lprng
[homes]
comment = Home Directories
read only = No
create mask = 0640
directory mask = 0750
browseable = No
[printers]
comment = All Printers
path = /var/tmp
create mask = 0600
printable = Yes
browseable = No
[incoming]
comment = Put incoming for me here.
path = /home/me/incoming
read only = No
guest ok = Yes
[testpr]
comment = Testprinter on ev-i02
guest ok = Yes
printable = Yes
print command = mv %s %U-%s
lpq command =
lprm command =
----------------------------------------
With this configuration file I put a word doc-file into the share
incoming, open the file using MS word 2000 or XP.
Then I print to printer testpr on the host (using some postscript printer
setting...)
After printing I change and save the file.
After three or four rounds doing printing, changing, saving either word is
unable to save the file or the spooling service of Win XP hangs.
On the server, the the bad file descriptor errors occur or contents of the
log file are appended to the catched print jobs etc...
(Sometime the print job is appended to log.smbd...)
Changing to
lpq command = /bin/echo
solves the problem and everything works fine.
I hope this will help to solve the described bug in samb-2.2.5.
Please feel free to contact me, if some needs mre information on this.
Best regards,
Wolfgang
More information about the samba-technical
mailing list