Toon posts:

[debian] samba traag?

Pagina: 1
Acties:

donderdag 30 januari 2003 10:53

Acties:

Verwijderd

Topicstarter
Ik heb op mijn server samba draaien, dit werkt lekker. Nou heb ik dus een map (op de server) geshared. Als ik nou via Win2k bestanden ga openen/bewerken, dan duurt het 5 seconden voordat hij de bewerking uitvoert. Zou het aan mijn config kunnen liggen?

hieronder mijn samba.conf

http://members.lycos.nl/debianforum/samba/smb.conf

donderdag 30 januari 2003 11:11

Acties:
  • Wilke
  • Registratie: December 2000
  • Laatst online: 09:27

Wilke

Waarschijnlijk zit het 'm in het resolven van de naam van de client (aan de serverkant).

Zie de NOS FAQ: Wat is mijn SSH/FTP verbinding toch traaaaaag!.

donderdag 30 januari 2003 11:22

Acties:

Verwijderd

Hoe hoog is je load?
# Most people will find that this option gives better performance.
# See speed.txt and the manual pages for details
# You may want to add the following on a Linux system:
# SO_RCVBUF=8192 SO_SNDBUF=8192
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192

donderdag 30 januari 2003 11:22

Acties:

Verwijderd

Topicstarter
Verwijderd schreef op 30 januari 2003 @ 11:22:
Hoe hoog is je load?


# Most people will find that this option gives better performance.
# See speed.txt and the manual pages for details
# You may want to add the following on a Linux system:
# SO_RCVBUF=8192 SO_SNDBUF=8192
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
Heb ik al aanstaan in SMB.CONF


hieronder mijn logbestand

code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42

[2003/01/29 22:12:29, 0] locking/posix.c:posix_fcntl_lock(663)
  posix_fcntl_lock: WARNING: lock request at offset 0, length 2225 returned
[2003/01/29 22:12:29, 0] locking/posix.c:posix_fcntl_lock(664)
  an Invalid argument error. This can happen when using 64 bit lock offsets
[2003/01/29 22:12:29, 0] locking/posix.c:posix_fcntl_lock(665)
  on 32 bit NFS mounted file systems.
[2003/01/29 22:12:29, 0] locking/posix.c:posix_fcntl_lock(663)
  posix_fcntl_lock: WARNING: lock request at offset 0, length 2225 returned
[2003/01/29 22:12:29, 0] locking/posix.c:posix_fcntl_lock(664)
  an Invalid argument error. This can happen when using 64 bit lock offsets
[2003/01/29 22:12:29, 0] locking/posix.c:posix_fcntl_lock(665)
  on 32 bit NFS mounted file systems.
[2003/01/29 22:12:30, 0] locking/posix.c:posix_fcntl_lock(663)
  posix_fcntl_lock: WARNING: lock request at offset 2206, length 1 returned
[2003/01/29 22:12:30, 0] locking/posix.c:posix_fcntl_lock(664)
  an Invalid argument error. This can happen when using 64 bit lock offsets
[2003/01/29 22:12:30, 0] locking/posix.c:posix_fcntl_lock(665)
  on 32 bit NFS mounted file systems.
[2003/01/29 22:12:30, 0] locking/posix.c:posix_fcntl_lock(663)
  posix_fcntl_lock: WARNING: lock request at offset 0, length 2207 returned
[2003/01/29 22:12:30, 0] locking/posix.c:posix_fcntl_lock(664)
  an Invalid argument error. This can happen when using 64 bit lock offsets
[2003/01/29 22:12:30, 0] locking/posix.c:posix_fcntl_lock(665)
  on 32 bit NFS mounted file systems.
[2003/01/29 22:26:43, 1] smbd/service.c:make_connection_snum(681)
  michielpc (192.168.1.16) connect to service webpages initially as user nobody (uid=65534, gid=65534) (pid 4777)
[2003/01/29 22:27:39, 1] smbd/service.c:close_cnum(854)
  michielpc (192.168.1.16) closed connection to service webpages
[2003/01/29 22:44:03, 1] smbd/service.c:make_connection_snum(681)
  michielpc (192.168.1.16) connect to service webpages initially as user nobody (uid=65534, gid=65534) (pid 4777)
[2003/01/29 22:44:44, 1] smbd/service.c:close_cnum(854)
  michielpc (192.168.1.16) closed connection to service webpages
[2003/01/29 22:55:02, 1] smbd/service.c:make_connection_snum(681)
  michielpc (192.168.1.16) connect to service webpages initially as user nobody (uid=65534, gid=65534) (pid 4777)
[2003/01/29 22:55:36, 1] smbd/service.c:close_cnum(854)
  michielpc (192.168.1.16) closed connection to service webpages
[2003/01/29 22:55:36, 1] smbd/service.c:close_cnum(854)
  michielpc (192.168.1.16) closed connection to service webpages
[2003/01/29 22:55:36, 1] smbd/service.c:close_cnum(854)
  michielpc (192.168.1.16) closed connection to service webpages
[2003/01/29 22:55:36, 1] smbd/service.c:close_cnum(854)
  michielpc (192.168.1.16) closed connection to service webpages


heeft het ook niets met de volgende optie te maken in SMB.CONF?

code:
1
2
3

# What naming service and in what order should we use to resolve host names
# to IP addresses
   name resolve order = lmhosts host wins bcast


Ik draai wel mijn eigen caching en interne DNS server....

[ Voor 13% gewijzigd door Verwijderd op 30-01-2003 11:28 ]

Reageer