FS#3743 - smbclient error messages

Attached to Project: Arch Linux
Opened by tranxene (tranxene) - Wednesday, 11 January 2006, 16:56 GMT
Last edited by Tobias Powalowski (tpowa) - Monday, 01 December 2008, 18:46 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity Low
Priority Normal
Reported Version 0.7.1 Noodle
Due in Version Undecided
Due Date 2006-01-11
Percent Complete 100%
Votes 0
Private No

Details

may be its just a matter of cosmetics, but every time i run smbclient i got this error messages:

params.c:OpenConfFile() - Unable to open configuration file "/etc/samba/smb.conf":
No such file or directory
creating lame upcase table
creating lame lowcase table
smbclient: Can't load /etc/samba/smb.conf - run testparm to debug it

i installed smbclient without the samba package...
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Monday, 01 December 2008, 18:46 GMT
Reason for closing:  Won't implement
Comment by Jan de Groot (JGC) - Thursday, 12 January 2006, 11:50 GMT
Does it continue without problems, even with this error message? If not, I think it would be a good idea to move smb.conf from samba into smbclient. Problem with that: it will overwrite user configured smb.conf, which is a very bad thing IMHO.
Comment by Judd Vinet (judd) - Friday, 13 January 2006, 00:14 GMT
The samba package doesn't not provide a smb.conf, only smb.conf.default. The user has to manually copy over the default and edit to his/her tastes.
Comment by tranxene (tranxene) - Saturday, 14 January 2006, 15:36 GMT
@Jan:

Yes, it continues without problems and a blank smb.conf solves the error message but not the "creating lame table" message which does not exist in standalone smbclients of other distributions.
Comment by Roman Kyrylych (Romashka) - Wednesday, 03 January 2007, 21:37 GMT
it could be solved by providing (secured) smb.conf in both samba and smbclient, I think.
Comment by Roman Kyrylych (Romashka) - Friday, 27 April 2007, 09:29 GMT
returning back here from http://bugs.archlinux.org/task/7012 :)
Ignore my previous message :) that will cause file conflict.
JGC: yes, it would be nice to move smb.conf from samba into smbclient. Why will that overwrite user configured smb.conf? We'll just put it into backup array. And smb.conf.default should be removed in favour of smb.conf (based on default, but more secure) IMO.
Comment by Greg (dolby) - Sunday, 22 June 2008, 15:46 GMT
Any news on this?
Comment by Gavin Bisesi (Daenyth) - Tuesday, 07 October 2008, 15:34 GMT
Bump.
Comment by Tobias Powalowski (tpowa) - Wednesday, 08 October 2008, 06:42 GMT
imho it cannot be fixed we don't provide a smb.conf file

Loading...