Help with setting up anonymous shares

[kin0kin]

these are the sample shares that I have:

 

\\tower\Tv Series
\\tower\Movies
\\tower\DVD

 

Under user shares in unraid menu, I've set them to export read/write.

 

Having done this, I'd need to provide a login name and password to access the shares, and all these shares. However, I wanted to make them read-only for anybody without a login credential, so I downloaded anonymous.sh and placed it into /boot/config. I then went into telnet and set chmod +x anonymous.sh. In my go script, I have added

 

/boot/anonymous.sh -s "Movies|Tv Series|DVD"

 

After rebooting unraid, all the shares are showing in network computers/tower. However, if I try to access it, it asks me for login username/password. So I take it that the line in go script didn't work.

 

I then went into telnet and manually entered

 

/boot/anonymous.sh -s "Movies|Tv Series|DVD"

 

and the script has set everything to guest ok.

 

What have I done wrong with the goscript?

[kin0kin]

Next question I have is that, assuming I had:

\\tower\Tv Series
\\tower\Movies
\\tower\DVD

and

\\tower\Restricted content

 

I have set "Restricted content" to export read/write, hidden. Having done that, the share does not show up in network\Tower. I assume the only way I can access it is to manually map the drive?

 

Now, after I mapped the drive, it prompted me to enter a login credential since it wasn't "guest ok". Upon entering an account that has access to it i.e. "root", the login credential is then automatically replaced/used in all other shares. Now I have complete rear/write access to everything. Is it possible to keep

 

\\tower\Tv Series
\\tower\Movies
\\tower\DVD

 

logged in as guest, with read only access, while keeping

 

\\tower\Restricted content

logged in as root?

 

The reason I am asking this is because in the event that I had to access the Restricted content folder in a root account to manage certain files. After managing the files and disconnecting the mapped drive, the whole system is still logged in as root. This would mean that if I wasn't careful, the guest PC now has full read/write access to all the folder...which can't be good.