Displaying 20 results from an estimated 3000 matches similar to: "2.0.4b: SERIOUS character set problem"
1999 Apr 20
0
2.0.3: character set problem
I've already posted about this to the samba list (19990201) then to samba-bugs
(19990301); no response, so I retry here.
I have
character set = iso8859-1
client codepage = 850
With samba 1.9.18p8:
smbstatus showed the filenames with localized characters ok (ie:
libert?.txt); smbclient was ok.
With samba 2.0.0 through 2.0.2:
if I connect with smbclient to a Samba share I see those characters
1999 Jul 10
5
2.0.4b: logrotate problems with rh60
The 2.04b rpm for rh60 ships with and installs a config file for logrotate
(the samba.log file in the packaging/RedHat section).
=====
/var/log/samba/log.nmb {
postrotate
/usr/bin/killall -HUP nmbd
endrotate
}
/var/log/samba/log.smb {
postrotate
/usr/bin/killall -HUP smbd
endrotate
}
=====
1)
I think that the use of "endrotate" is wrong.
There is no
1999 Feb 01
0
2.0.0: lost localized characters in smbstatus
linux 2.0.35, samba2.0.0 compiled from tgz.
I have:
character set = ISO8859-1
and
client codepage defaults to 850, so that testparm shows
client code page = 850
With samba 1.9.18p8, smbstatus showed the filenames with localized characters ok (ie:
libert?.txt)
I use the same smb.conf with 2.0.0
Now, with samba 2.0.0, if I connect with smbclient to a Samba share I see those characters
ok, but
1999 Jul 17
0
2.0.4b: logrotate problems
On 18 Jul 99, giulioo@tiscalinet.it (Giulio Orsero) had questions
about 2.0.4b: logrotate problems:
[snip]
> As I said, my problem was not that logrotate didn't rotate; but
> thet after logrotate rotated a log smbd kept logging to the
> rotated file instead of to the newly created, empty, log.smb. The
> newly created log.smb remained empty forever, till I restarted
> smbd.
1999 Jun 28
1
2.0.4b/rh60/smbstatus: European characters (accented) (PR#18293)
giulioo@tiscalinet.it wrote:
> SOLUTION:
> for samba 2.0.x I need to use
> smbstatus|tr '\205\212\215\225\227\202' '\340\350\354\362\371\351'
> and all is ok :-)
>
> If someone can explain me this I'm still waiting :)
Try adding the following patch to 2.0.4b. This should
fix the problem and will be in the next release.
Regards,
Jeremy Allison,
Samba
1999 Nov 17
4
2.0.6: HUP/charset/profiles/smbmount/logging
This is the list of problems I had with samba-2.0.6 so far. Can anyone
tell me if he can reproduce them and if he considers them as problems?
2.0.6 on linux 2.2.13 or 2.0.33
1)
sighup/log reopening doesn't always work: connections that are already
active keep logging to the old logs; logrotate rotates/zip the logs and
samba stops logging completely till restart.
2)
Localized chars.
I have
1999 Nov 12
3
problems running samba on Caldera 2.3?
I have the default installation of samba (2.0.5) that came with Caldera OL
2.3, but it doesn't seem to be starting up properly, nor is SWAT working.
When I run the script 'samba start', I get the message "Starting samba:
smbd nmbd", but when I check the running processes, only nmbd shows up.
Running smbstatus gives me the message "Couldn't open status file
1999 Jun 25
1
2.0.4b/rh60/smbstatus: European characters (accented)
character set = iso8859-1
client code page = 850
Through win9x I save a file, whose filename contains characters as: ? ? ? ? ?,
on a samba share.
I can see those filenames (on a samba share) ok through win9x explorer.
I can see those filenames ok through ls on linux.
If I open one of those file, and then look at locked files with smbstatus,
they are showed with a LF in place of the localized
1999 Jul 02
0
Jeremy, please: your opinion about oplock_break :-)
Many 2.0.x users have the:
[1999/06/23 10:47:48, 0] smbd/oplock.c:oplock_break(773)
oplock_break resend
[1999/06/23 10:47:58, 0] smbd/oplock.c:oplock_break(773)
oplock_break resend
[1999/06/23 10:48:08, 0] smbd/oplock.c:oplock_break(773)
oplock_break resend
[1999/06/23 10:48:18, 0] smbd/oplock.c:oplock_break(790)
oplock_break: receive_smb timed out after 30 seconds.
problem.
I get this
1999 Jul 18
0
2.0.5-pre3: torture.c doesn't compile on rh60
rh60/2.2.10-ac10
Compiling utils/torture.c
utils/torture.c: In function `run_browsetest':
utils/torture.c:929: invalid type argument of `->'
utils/torture.c:934: invalid type argument of `->'
utils/torture.c: In function `create_procs':
utils/torture.c:1118: warning: initialization discards `volatile' from pointer
target type
utils/torture.c:1118: warning: passing arg 1
1999 Oct 28
0
AW: SAMBA digest 2286
Hey, digest 2286 incomplete, only first 3 topics contained. Can I get a new
copy ?
Thanks,
Hans-Joerg Glock
> -----Urspr?ngliche Nachricht-----
> Von: samba@samba.org [SMTP:samba@samba.org]
> Gesendet am: Mittwoch, 27. Oktober 1999 22:12
> An: Multiple recipients of list SAMBA
> Betreff: SAMBA digest 2286
>
> SAMBA Digest 2286
>
> For information on
1999 Jul 16
9
SWAT issue
I have had a RH5.2 server running Samba up for a long time. I upgraded to
Mandrake 6.0. It broke Samba, so I reinstalled using the RPM on the CD.
Samba works just fine, but SWAT will not! If I try to start it manually
(/usr/sbin/swat) it just hangs.
In /etc/services I have a line like this:
swat 901/tcp
In /etc/inetd.conf I have:
swat stream tcp nowait.400 root
1999 Nov 23
0
Help me too! Password Authentication Failure
I have a similar problem to Giulio Orsero.
I have failure messages in the log files, but I actually have samba mapping
failures. A PC will map every day for two weeks properly and then not connect.
Fifteen minutes later, it will connect. Any suggestions?
Alvin
----------
Giulio Orsero <giulioo@tiscalinet.it>
7)
I have 2.0.6-PDC and a 2.0.6-domain-member of the 1st pdc.
1999 Jul 21
0
2.0.5: problem with HUP reopening logs
rh60/caldera1.3
2.0.x (before 2.0.5) PROBLEM: samba didn't reopen then logs after HUP.
I posted about this to samba-bugs; AT corrected the problem in 2.0.5-preXX,
but not completely it seems.
2.0.5 PROBLEM: samba reopens the logs after a HUP but logs only the first
connection to the new log, then it keeps logging to the old one.
Here is what I see:
# pwd
/var/log/samba
# smbclient|grep
1999 Jul 20
0
2.0.x: terribly slow smbclient tar extension
Since the release of the first 2.0.x (jan1999) I noted that
smbclient '\\server\share' -Tx filename.tar
was terribly slow.
smbclient '\\server\share' -Tc filename.tar
is as fast as 1.9.18.
If I use smbclient from 1.9.18 the performance is high (with the same target
pc).
These are some tests with:
- Win98pc
- lan 10Mbps
- samba-2.0.5-pre4/rh60
- a dir containing 1,2MB in 52
1999 Aug 04
0
samba-2.0.4b/NT4.0(SP3): share name
Hello, everyone. Could you help me to solve the problems?
Recently I downloaded samba-2.0.4b souce and after I compiled it, I used it
as
a replace of samba-1.9.18p8.
The smb.conf file was used as before. But there are two problems to me.
1)When I used samba-1.9.18p8, the Windows NT4.0(sp3) workstation can browse
the share names of Japanese SJIS, but now I couldn't access the shares
because
1999 Aug 04
0
samba-2.0.4b/NT4.0(SP3): share name (PR#19444)
szcathay@public.szonline.net wrote:
>
> Hello, everyone. Could you help me to solve the problems?
>
> Recently I downloaded samba-2.0.4b souce and after I compiled it, I used it
> as
> a replace of samba-1.9.18p8.
> The smb.conf file was used as before. But there are two problems to me.
> 1)When I used samba-1.9.18p8, the Windows NT4.0(sp3) workstation can browse
> the
1999 Jun 23
1
oplock_break: client failure in break - shutting down this smbd.
2.0.4b, RH60 (2.2.6+raid1, non root-raid), accessed from win98/ie5.
Intermittently ie5 takes very long to load an html page from samba; at the
same time it loads another html page ok from another linux/samba1.9.x
At 10:47:34 I click on the html page and it is loaded at 10:48:18.
[1999/06/23 10:47:34, 1] smbd/service.c:make_connection(488)
go (10.0.0.115) connect to service go as user go
1999 Jun 20
2
newbie: where and how to use smbmount with 2.04b ?
Fellow Samba-ists,
I read about smbmount
But I cannot find it in 2.04b
Where and how do I use it ?
Regards
Terence
2003 Dec 01
0
No subject
vl
by samba.anu.edu.au with ESMTP id <S12875607AbPJPKg0>;
Sat, 16 Oct 1999 20:36:26 +1000
Received: from i3.golden.dom ([212.216.109.2]) by fep09-svc.tin.it
(InterMail v4.01.01.02 201-229-111-106) with ESMTP
id <19991016103606.RHGY435.fep09-svc@i3.golden.dom>
for <samba@samba.org>; Sat, 16 Oct 1999 12:36:06 +0200
Received: from pc79