WaltS48 wrote:
On 10/12/17 2:59 PM, Rob Steinmetz wrote:
Jonathan N. Little wrote:
Rob Steinmetz wrote:
I have a server that had a problem with a share. I think I have fixed
that but my users cannot access their existing SeaMonkey Profiles. They
are located on a a SAMBA [homes] share on an Ubuntu 16.04 LTS server in
a directory called ~/.seamonkey.
In the past I have been able to conned to theses existing profiles by
logging into the Profile Manager and simply pointing to the existing
SeaMonkey profile.
However when I do this on on this server now I get a SeaMonkey opening
page and SeaMonkey does not recognize the existing email configuration.
Okay if profiles are on a server and not on local system, if I am
understanding you correctly, then I need some more information.
Firstly, most likely on the client machines one issue is the profile.ini
must be set to absolute paths:
IsRelative=0
The typical profile.ini from a working machine looks like this.
[General]
StartWithLastProfile=1
[Profile0]
Name=default
IsRelative=1
Path=Profiles/tcq542gy.default
[Profile1]
Name=rob
IsRelative=0
Path=U:\.seamonkey
That appears to show that rob is using Profile1(with no name)from drive
U: and launching SeaMonkey using the .seamonkey command.
Neither profile has Default=1 in the file.
That is confusing.
I diidn't past the entire file.
Secondly, are you sure the path is '~/.seamonkey'? Mine, set as default
is '~/.mozilla/seamonkey'.
I'm very sure.
The path to my SeaMonkey profile on Ubuntu also is
/home/username/.mozilla/seamonkey.
If I right click on the seamonkey folder and view the Properties, there
is a Local Network Share tab with a Share this folder setting that isn't
enabled.
Maybe you need to check that?
The share is enable and I can access it.
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
