Samba and SMBFS...

[flaviosr]

Hi to all,
I configured Samba and it's ok! I can ping, the Amiga is seen and the sun is shining... :-)
But when I try to use SMBFS I have some problems:
° I made small scripts to "see" some PCs but only few times these scripts works... most of the times nothing happens and some the computer hangs;
° if I copy these scripts in a CLI shell everything is ok!
ARGH!!! What am I missing?

Another help: is it possible to disconnect a connection? If I stop Miami while a connection is on, the computer hangs most of the times...

Thanx

[doctorq]

I'm mounting SMBFS shares fine through scripts, so can you give an example of your script that doesn't work?

FYI, you actually don't need Samba installed for using SMBFS.

As for stopping a share, RTFM. Write Status in CLI to see which process you have to break, and then write Break to break the connection.

[Piru]

smbfs needs stack of at least 32768 bytes.
You can disconnect by sending CTRL-C to smbfs process.

[flaviosr]

I'm mounting SMBFS shares fine through scripts, so can you give an example of your script that doesn't work?

FYI, you actually don't need Samba installed for using SMBFS.

As for stopping a share, RTFM. Write Status in CLI to see which process you have to break, and then write Break to break the connection.

My script is very easy, changed today to the following line:
RUN SMBFS Volume="name volume" Workgroup=WORKGROUP Service=//computer/directory

I also changed stack to 32768...

Most of the times it hangs and only some it works...
First I had also >nil: but without it I can CTLR+C to stop!

If I copy the line to a CLI line everything works always (apart my CTRL+C problem... if I close this way the PC hangs...).

Since I am not so good in AmigaOS:
° I created the file with editpad and saved it;
° I opened the info for the file;
° I have the "V" (I do not know the word in English!) for script and removed the one for executable;
° I changed the stack today to 32768;
° Priority 0???
° Have I to executo from Workbench? Now I have this doubt... is it better to run from CLI?
° I change the association from editpad to iconx...

anf, anf, anf...

Where am I wrong?

[doctorq]

I can't tell you were you are going wrong, but for me, it works by either starting the script from an icon or starting the script from CLI.

I always use Run >NIL: to start it, as I don't want to have 4 open windows telling me the same thing, for the 4 shares I usually mount. If I really need to disconnect one of the drives, I use the break command instead.

I have the following text in one of my script files.

Run >NIL: C:SMBFS Workgroup=MSHOME User=PCGuest Service=//Desktop/Amiga Device=Amiga_SHARE: volume="Amiga on Desktop"

I use StackAttack, so the stack size is taken care of automatically. I use version 1.66 of SMBFS.

[Piru]

I use StackAttack, so the stack size is taken care of automatically.

You really waste 32k stack for each and every process? Sounds like huge waste to me.

[doctorq]

And yet, I still have more than 200 MB free fast ram left, so I can live with it :-)

[olsen]

Hi to all,
I configured Samba and it's ok! I can ping, the Amiga is seen and the sun is shining... :-)
But when I try to use SMBFS I have some problems:
° I made small scripts to "see" some PCs but only few times these scripts works... most of the times nothing happens and some the computer hangs;
° if I copy these scripts in a CLI shell everything is ok!
ARGH!!! What am I missing?

Are you sure that everything always works if you launch smbfs manually?

There's a potential issue with name resolution. If you don't have a DNS entry set up for each server you want to connect to, smbfs will fall back to sending broadcast name queries through the network in the hope that the server you want to connect to will respond. This may not always work. In fact, depending upon your TCP/IP stack it may not work at all. The reason why it may not work is because the TCP/IP stack may not be able to send the broadcast query to the right place due to a bug in the old TCP/IP code.

Anyway, a workaround for this name resolution issue is to use the IPv4 address of the server instead of trying its name.

So... the next question would be: how do you launch smbfs if you don't enter the command manually?

[motorollin]

You really waste 32k stack for each and every process? Sounds like huge waste to me.

And yet, I still have more than 200 MB free fast ram left, so I can live with it :-)

But it's the principle!

--
moto

[doctorq]

But it's the principle!

Again, four chunks of 32k really can't piss me off.

[Golem!dk]

Again, four chunks of 32k really can't piss me off.

So you only have four active processes at any given time?

[pVC]

For breaking certain smbfs mount I use this script (launched from dopus startmenu):

status com "smbfs '//remotesystem/share'" > T:smbfs_pid
break ? < T:smbfs_pid >NIL:

[flaviosr]

Are you sure that everything always works if you launch smbfs manually?

There's a potential issue with name resolution. If you don't have a DNS entry set up for each server you want to connect to, smbfs will fall back to sending broadcast name queries through the network in the hope that the server you want to connect to will respond. This may not always work. In fact, depending upon your TCP/IP stack it may not work at all. The reason why it may not work is because the TCP/IP stack may not be able to send the broadcast query to the right place due to a bug in the old TCP/IP code.

Anyway, a workaround for this name resolution issue is to use the IPv4 address of the server instead of trying its name.

So... the next question would be: how do you launch smbfs if you don't enter the command manually?

Bad news (for me)... I made more tests and SMBFS hangs also when launched from CLI but not so often when lauched with a script!
I tried with IP address instead than name but I had no results!
I tried passing from SMBFS 1.74 to the older 1.66 but again no results.
If I use device and service together the Amiga hangs immediately!!!
When I launch a script nothing happens... but if I open a CLI and try to "enter" the new device I receive a memory error!!! :-o
I am using a standard 18 Mb A4000T, could it be not powerful enough?

Another question: are you using Miami or Genesis?
Which is better?

[motorollin]

Again, four chunks of 32k really can't piss me off.

Clearly text alone is insufficient to communicate sarcasm

[Daedalus]

Shameless plug here, but you could try my little GUI for SMBFS (Aminet clicky!)... It runs as a commodity, tracks your shares and allows you to mount and dismount them at a click. It doesn't use encryption and passwords are plain to see when you configure it, so it's not for the security-conscious, but it might make things a little easier for you.

I use it all the time and it works great for me, but I use it on OS4 with Roadshow. From my OS3.9 days though, I found that AmiTCP/Genesis to be faster for Samba transfers and general use. Miami of course was much more flexible and so was my only option when connection to some unusual networks.