Hello,
using redhat 8. sesame designer/new application i get error 'cannot save to specified directory'. the directory is following:
/usr/local/sesame/test/.
file permissions are user:root and group:sesame have ful lpermissions. i am logged in as member of group. thanks--joe

hmmm--i am having trouble starting from the command line as follows:
/usr/local/sesame/sesame server test_server
"failure while loading database test_server"
anyway--here is the result of ls -la
[root@testserver sesame]# ls -al
total 6160
drwxrwxr-x  6 root  sesame    4096 Jul 13 23:51 .
drwxr-xr-x 13 root  root      4096 Jul 13 23:01 ..
drwxrwxr-x  2 root  sesame    4096 Jul 13 23:51 asc
drwxrwxr-x  2 root  sesame    4096 Apr  6 14:57 Docs
drwxrwxr-x  2 root  sesame   12288 Dec 15 2003  HelpFiles
-rwxrwxr-x  1 root  sesame   14271 Apr  6 10:34 lock_status
drwxrwxr-x  2 root  sesame    4096 Jul 13 23:50 test
-rwxrwxr-x  1 root  sesame      23 Dec 14 2003  rootdirs.ini
-rwxrwxr-x  1 root  sesame 3373027 Apr  6 12:18 sdesigner
-rwxrwxr-x  1 root  sesame 2834187 Apr  6 12:18 sesame
-rwxrwxr-x  1 root  sesame    3262 Apr 28  2003 sesicon3.ico
-rwxrwxr-x  1 root  sesame   14396 Apr  6 10:34 sunlock
-rwxrwxr-x  1 root  sesame   14367 Apr  6 10:34 s_version
   cannot save to /usr/share either... thanks. joe

Can you send me the ls -la for the directory "/usr/local/sesame/test"?

If you "su" and "cd /usr/local/sesame" and then launch Sesame with "./sesame" are you able to write to "/usr/local/sesame/test" as the root user?

Quote:

I see the "ls -la" for "/usr/local/sesame", but no the "ls -la" for "/usr/local/sesame/test" - the content of the "test" directory.
Quote:

Yeah, we know. I think it is posted in the errata, addendum, or workarounds page. I can't remember which.
Quote:


That would mean that your account does not have permission to open either the default ports or does not have permission to open the default network device. Is this your computer? If so, you will have to make changes in the /dev directory or in the /etc directory (usually through the admin user interface) to tell the firewall/IP chaining, that you are activating the default ports for Sesame (20000, 20001), or whatever ports you choose to use. You can put an entry in for Sesame in the /etc/services file to indicate the default ports you would like to use. If it is not your computer and you cannot log in as root, you will need to speak to the system administrator and have them make the appropriate settings.

If you change the ports the server is defaulting to, you must also specify those same ports on the client:

sesame -client server_name:20020:20021

You don't need to create a new user for sesame. It will be run (as any executable on Unix) with the permissions of the user that launched it. Try launching it as root (as an experiment), since we know that root can write to that directory. If sesame run from root can write to that directory, then it is a directory permission problem. If it can't, see if you can create a file in that directory by hand as yourself or as root. If you can create a file there, but Sesame running as root cannot, then it is a path problem. The path will appear in the dialog box near the bottom right. Before you click on anything in the dialog box, what does it say? Are /usr/local/sesame and /usr/local/sesame/test in your rootdirs.ini file?