SaMBa V2.2.5

[Jettah]

Hi,

I just installed SaMBa V2.2.5 on my A1200. I must say that it is bloody fast! Used to use V2.0.0 as supplied with the X-Surf board. It is really beond compare. Try it! Good work,  Olaf.

But nothing comes without a bit of hassle. All of a sudden this new setup makes my computer rattle like snake. Equipped with an O-fourty it reaches nearly 100% CPU-usage according to XOper. It is all consumed by:
-   scsi.device
-   dh4 {dh4:}
- 3 [ workbench ] workbench
- 6 [ smbd ] netbios-ns

The latter one flips in and out of the queue. This makes me think that it is constantly loading and stopping on a repetitive base.

What can I do to stop this behaviour? Any idea is welcome!

Regards,

Jettah

[Jettah]

@KennyR

But there's a new port for 2.2.5 for 68k, at amigaos.dk. I've just installed it and it works great.

This is exactly the one I use for the A1200!

In my UserStartup I've put these lines:
assign Samba: <FullPathName>
path Samba:bin ADD
Resident smbd pure

The latter line prevents the excessive disk accesses as the program is already in memory (README says that smbd is both reentrant and some other thing and can therefore be made resident).

But it still exits with code 0x01 (showing in the Genesis logfile)and then starts again. Not immediately, you know, but after some time (10 minutes, 15 minutes?). And from then onwards every somany seconds. :-?  :-?

With the old setup (V2.0.0) I once had a similar problem and I forgot what I did to overcome this behaviour, but I know it can be cured.


Regards,

Jettah

[Jettah]

@All interested

Probably found the culprit. Some part was looking for these files:
- Samba:log/locks/smbd.pid
- Samba:log/locks/nmbd.pid

In Samba:log/log.nmbd there was repeatedly an addition of a line like this:
ERROR: Can't open /samba/log/locks/nmbd.pid: Error was No such file or directory

Cured it by simply copying those files from the old setup...

Case closed.

Thanks,

Jettah