|
|
Mozilla is an award-winning open source
cross platform Internet application suite including a web browser,
e-mail client, address book, web page composer and chat application
with extensive international support. Special features include: Profile
Roaming, and Accessibility features. For details please visit: www.sun.com/mozilla
Release Notes
What's new? (What's different from last
version and why you should upgrade.)
What is different from the community version of
Mozilla?
Installation
Guide
Step by step installation instructions for Mozilla
1.7 for Sun Java™
Desktop System (Solaris Operating System Edition)
Troubleshooting
Guide
Having technical difficulties? Consult the
troubleshooting guide to find a solution.
Feedback
We want to hear from you!
Support
Mozilla
1.7 is covered by Sun Services' support offerings for the Solaris OS.
If you already have a support contract for Solaris OS, you are entitled
to support.
For more information about Sun Services and its support
offerings, visit
http://sun.com/service/support/software
Copyright 2005 Sun Microsystems, Inc., 4150 Network Circle,
Santa Clara, California 95054 U.S.A. All rights reserved. Sun, Sun
Microsystems, Java, SunOS, OpenWindows, and Solaris are trademarks,
registered trademarks, or service marks of Sun Microsystems, Inc. in
the U.S.A. and other countries. All SPARC trademarks are used under
license and are trademarks or registered trademarks of SPARC
International, Inc. in the U.S.A. and other countries. Products bearing
SPARC trademarks are based upon an architecture developed by Sun
Microsystems, Inc.
What's New?
As
always the Sun Mozilla team strives to bring you new releases with
changes to improve performance, stability, web site compatibility,
standards support, and usability.
Non-standard Website Manager
Some Web pages do not comply with the W3C standard. These
Web pages may
or may not display correctly. Sun's Mozilla has introduced the ability
to safely deal with many of the non-standard web-elements.
Accessibility
Mozilla has been designed for productive use by users with
disabilities. It is completely keyboard navigable and supports
assistive technologies that use the GNOME accessibility architecture,
in particular the Gnopernicus screen reader and magnifier and the GNOME
On-screen keyboard.
Security
Cross-platform authentication support using Kerberos (GSSAPI)
and NTLM
Printing
Printing of the list of attachments in an e-mail message is
now supported.
Roaming
Access your personalized settings from
anywhere (bookmarks, preference, address book etc...)
Performance
Size and performance have improved dramatically.
Mail
One
of the most requested Mozilla Mail features, an option to separate the
Recipient and Sender columns in the thread pane, has been implemented
Java
Easily switch between multiple JRE versions
Liveconnect
Improved support and reliability for liveconnect across
domains.
Want More?
For more details please visit http://wwws.sun.com/software/solaris/browser/
or http://www.mozilla.org/
What is the difference between
the Sun release of Mozilla and the community release?
System Integration
Unified UI Seamless integration
File associations - Mozilla can directly call
other programs to open various files received in email or while
browsing
Menu bar - Mozilla can be launched directly
from the Menu bar
Roaming
Access your personalized settings from anywhere
Compatibility - Compatible with Java
Enterprise and standard FTP servers , supports HTTP, LDAP and FTP
protocols
High availability- Access your bookmarks,
preference, address book anywhere, anytime
Reliable - made some changes? Conflict
resolution to avoid problems with multiple access
Non-Standard Web Site Manager
Smoother Surfing
Site Manager: Sun has added
this new feature to make surfing non-standards compliant webpages
easier to view. End users
will be able to enable/disable these extensions on a per site basis.
Accessibility
Enabling all people the freedom to use all of the
functionality of the Mozilla web browser
Visual - Supports large fonts and high
contrast themes compatible with Gnome
Keyboard navigation - all Mozilla browser
functions can be accessed through keyboard alone (mouse not required)
Assistive Technologies
- Supports the gnome accessibility framework in order to work with
assistive technologies (screen reader, screen magnifier, onscreen
keyboard) that will appear in future versions of the Gnome desktop.
Printing
Print multi-language pages
True Type printing - Sun
Mozilla generates a postscript file which does not require extra
configuration to print non-western languages
Bug FIXES!
Sun's Mozilla - Contains hundreds of bug
fixes not found in the community version
Known Issues
CDE
When color depth is set to 256 colors (8 bit), UI
will not display correctly.
If color depth is set to 24 bit or higher, this problem will not occur.
Note:
To check your current settings use: fbconfig -prconf
To change your current settings use fbconfig -depth <desired color
depth>
Real Player
Real Player 8.0 plugin will hang when certain
Solaris patches are applied. See Bug 126310
Directly clicking on a linux package file
(.rpm) will crash Mozilla,
because both web servers and Mozilla register .rpm as RealPlayer media,
but RealPlayer plugin can not handle invalid rpm file correctly and
will crash taking Mozilla with it. Users can work around this by right
clicking the link and select "Save Link Target As..." from the popup
menu instead. See bug: http://bugzilla.mozilla.org/show_bug.cgi?id=215999
Profile
If your profile is corrupted, it can cause unexpected
errors in Mozilla.
If this happens, create a new profile
International Domain Names & Bookmarks
URLs Book marks may not display correctly when using IDN
and you may not be able to access the URL through the bookmark
This can be resolved by manually editing the bookmark
Hindi
In all dialog boxes, numerical information does not appear
in Hindi
System Requirements
Minimum requirements
OS - Solaris 8 Operating System
Desktop - GNOME 2.0 or CDE (
Common Desktop Environment)
Memory: 128 MB
Disk space:
SVR4 - Final size on disk 74MB
(254MB required during installation, space can be
recovered)
Library - GTK2 library
Note: The GNOME 2 desktop
includes the GTK 2 library; this library may also be installed with the
Mozilla installer.
Java - JRE 1.4.2_02
Patches
It is strongly recommended that you apply the following
patches to your system
Solaris 8 SPARC
108652-66, 108921-16, 112003-03, 108773-18, 111310-01, 112472-01,
108714-07, 111111-03, 112396-02, 108940-54, 108987-13, 108528-22,
108989-02, 110380-04, 110934-10, 109147-24, 111308-03, 112438-01,
110386-03, 111023-02, 108993-22, 108434-14, 108435-14, 109159-03,
109704-03, 111721-04, 113261-02, 114542-01
Solaris 8 x86
108653-55, 108922-16, 108774-18, 111307-04, 111311-01, 112473-01,
112439-01, 108715-07, 111112-03, 112397-02, 108941-54, 108988-13,
108529-22, 108990-02, 110403-04, 110935-10, 109148-24, 111309-03,
110400-01, 111024-02, 108994-22, 108436-13, 109160-03, 109705-03,
112757-01, 113262-02, 114543-01
These patches can be obtained from:
http://sunsolve.sun.com/pub-cgi/show.pl?target=patchrpts/8
or
http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-access
Solaris 9 SPARC
111711-08, 111712-08, 111722-04, 112661-06, 112785-34, 112963-10,
113902-03, 114276-02, 114641-02
For: Gnome 2.0.0 Sparc Patch ID: 114686-02
For: Gnome 2.0.2 Sparc Patch ID: 115738-03
Solaris 9 x86
111713-06, 111728-03, 112662-04, 112786-22,
113986-06, 113903-03,
114277-02, 114642-02
For: Gnome 2.0.0 Intel Patch ID : 114687-02
For: Gnome 2.0.2 Intel Patch ID : 115739-03
These patches can be obtained from:
http://sunsolve.sun.com/pub-cgi/show.pl?target=patchrpts/9
or
http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-access
Note:
#1: JRE 1.5 recommended and required patches are not
listed here, if you choose install bundled JRE 1.5.0_05, the Recommended
and required patches are now hosted for download on the SunSolve
website.
#2: When searching for a patch, in order to get the latest version,
don't input the version number, just the main patch number.
For example, use 108664 instead of 108664 -02, -xx is the version
number.
When patching, the -xx is the lowest accepted version, more recent
patches are also acceptable.
How to install Mozilla 1.7 for
Solaris OS - Web Start edition
After downloading Mozilla, perform the
following steps to install the application.
1. Use the following command to extract the files:
% unzip <installation package name>.zip
2. Change to the Mozilla installation directory:
% cd MOZinstaller
3. If there is no GTK2 library on your system, please perform steps 4
through 7
to install the library. Otherwise, go to step 8.
4. If you are not root already, become the root user by typing "su",
then type your root password.
5. Change to the GTK2 directory:
# cd GTK2
6. Run the GTK2 library install script:
# ./GTK2install
7. Change to the Mozilla installation directory:
# cd ..
8. Run the Mozilla 1.7 install script:
# ./installer
9. You will need to choose "Custom install" to install language
packages other than English.
10. Specify the directory to install Mozilla.
By default, a "Mozilla" directory will be
created in your home directory
and Mozilla will be installed there.
11. Select language packages which you want to install.
12. Follow the on-screen instructions to complete the installation
process.
Wait until you see the
"Installation Summary" window come up to inform
you whether the installation
was successful.
13. Click "Exit" to close Installer.
14. To start Mozilla, change to the
installation directory and run the
following program:
% ./mozilla &
If you do not have the GTK2 library on your system and directly run the
Mozilla installer script as a common user, you will see these messages:
"Sun Mozilla 1.7 requires the GTK2 library, you can install GNOME 2.0
which includes GTK2
or install GTK2 only"
"To install GTK2 only, you should go to the GTK2 directory and run
GTK2install as root".
How to install Mozilla 1.7 for
Solaris OS - SVR4 Packages
Make sure you have installed GNOME2 (which
includes GTK2) or the GTK2 library separately on your system.
1. Before unzipping the files make a directory to place the files
in, change to the new directory and unzip the files using the
unzip command.
% mkdir <new directory
name>
% cd <new directory name>
% unzip <installation package
name>.zip
2. If you are not root already, become the root user by typing "su",
then type your root password.
3. Install Mozilla by running the install script:
# ./mozinstall
Note - The Mozilla 1.7 packages will be
installed in
the /usr/sfw/lib/mozilla directory on your
workstation.
4 Install the language package
The installer prompts you with a list of languages
which you can install, enter the number corresponding to the language
package and hit enter.
Rrepeat this step for each language you want to add.
Enter 0 and enter to continue the installation.
5. Exit superuser by typing "exit" at the
prompt.
6. To start Mozilla, change to the
installation directory and run the
following program:
% ./mozilla &
Upgrading from
Mozilla 1.2.1/1.4 to Mozilla 1.7
SVR4 - If you installed
Mozilla 1.2.1/1.4 SVR4 packages (pkgadd version), you should remove
Mozilla
1.2.1/1.4 first using pkgrm as root and then install Mozilla 1.7.
Note: When
upgrading from an earlier version of Mozilla (to avoid incompatibility
problem with previous versions) the Mozilla installer will prompt you
to delete the install directory if it is not empty. Answer NO if you
put your profile or other personal files in the install directory,
otherwise the files will be deleted. Users who put profiles in the
default location are not affected.
Migrating from
Netscape 4.7x to Mozilla 1.7
If you decide to try out Mozilla 1.7 for
Solaris OS, it will
not affect your ability to use Netscape 4.7x. Both these applications
can be running at the same time.
However, it is not recommended to use two
mail clients simultaneously.
Netscape 4.7x and Mozilla 1.7 for Solaris write
the user's information (preferences, cache files, bookmarks) into
different directories:
Netscape 4.7x - under a ~/.netscape directory.
Mozilla 1.7 for Solaris - under a ~/.mozilla directory.
During the migration of your Netscape 4.7x
preferences such as bookmarks, proxy servers and email setup, a copy of
preference files, email setup and local mail folder is made by default.
The copy of local mail folders can waste lot of disk space and may be
undesired. We offer you two choices to control the behavior of local
mail folder migration.
Option #1: Re-use the old local mail
folders created using
Netscape 4.7x. In addition to saving disk space this allows one to
switch back and forth between Netscape 4.7x mailer and Mozilla mailer.
NOTE: There is a possibility of local mail
folder data
corruption if Netscape 4.7x and Mozilla mailers are run at the same
time using the same shared local mail folders.
Option #2: (Default) Keep the local mail
folders separate
from Netscape 4.7x and Mozilla 1.7 for Solaris to allow simultaneous
use of Netscape 4.7x and Mozilla mailers.
At the expense of extra disk
space and fragmenting the local mail folder, this option ensures that
you never lose any data stored in local mail folder.
The above choice is given to first time users of
Mozilla 1.7 who
are migrating from Netscape 4.7x. System administrators and Enterprise
administrators can make this decision for their wider user base.
They
can change the default settings for their users and choose to allow
them an ability to override the default (or deny override) using the
following preference settings.
To set the choice to option #1 and disallow
override ability to
your users, edit the file <Mozilla installation
directory>/defaults/pref/mailnews.js
pref("mail.migration.copyMailFiles", false);
pref("mail.migration.copyMailFilesPopupWindow", false);
To set the choice to option #1 but allow override
to users, edit
the file <Mozilla installation
directory>/defaults/pref/mailnews.js
pref("mail.migration.copyMailFiles", false);
pref("mail.migration.copyMailFilesPopupWindow", true);
Migrating from Netscape 6 or 7
to Mozilla 1.7
You
can safely install Mozilla 1.7 with Netscape 7. Mozilla can import user
data from Netscape 7; If you wish to migrate from Netscape 7 to
Mozilla, we recommend that you uninstall the Netscape 7 after you have
both installed Mozilla and have migrated your user data.
Your Netscape 6 or 7 profiles will be available to Mozilla.
However, sharing profiles between Netscape 6 or 7 and Mozilla can cause
problems.
Mozilla automatically uses your
Netscape profile unless you have multiple profiles, in which case
Mozilla prompts you to choose a profile. To avoid accidentally opening
Mozilla with your Netscape profile, create a new, extra profile using
your Netscape's Profile Manager before installing Mozilla.
Note: Upgrading
from netscape 6 or 7 (to avoid incompatibility problem with previous
versions) the Mozilla installer will prompt you to delete the install
directory if it is not empty. Answer NO if you put your profile or
other personal files in the install directory, otherwise the files will
be deleted. Users who put profiles in the default location are not
affected.
Note: It is strongly suggested that you do
not share profiles between Mozilla and Netscape 6 or 7
Adding Mozilla
to Your Path
Determine where your PATH variable is set and
add the Mozilla directory to your path, so you can start Mozilla by
typing "mozilla" in a terminal window. The path may be set in the
.dtprofile, .login, .bashrc or .cshrc file.
For bash shell:
export PATH=$PATH:<Mozilla installation directory>
For csh shell:
setenv PATH ${PATH}:<Mozilla installation directory>
Plugins
Download plugins, and
install in Mozilla's plugin directory
Mozilla's plugin directory
Mozilla will search for plugins in the following
directories:
1) The default plugins directory is in
<Mozilla installation directory>/plugins
2) The default user plugins directory is in $HOME/.mozilla/plugins
3) The user defined plugin directory could be set by an environment
variable "env: MOZ_PLUGIN_PATH"
For example "export MOZ_PLUGIN_PATH=~/download/plugins"
Java
The Java Plugin is enabled in Mozilla 1.7 by default.
If it doesn't work, make sure there is a symbolic link in the plugin
directory, which points to:
SPARC:
$JAVA_PATH/plugin/sparc/ns7/libjavaplugin_oji.so
x86:
$JAVA_PATH/plugin/i386/ns7/libjavaplugin_oji.so
Note: copying the file instead of making the
symbolic link will cause Java to crash
Real Player
Macromedia Flash
Adobe Acrobat Reader
Solutions
| Topic
|
Problem
|
Solution
|
Installation
|
|
|
Patches
|
Warning: Required patches are
not installed on the system
|
Install the necessary
patches. Latest patches can be found at:
http://sunsolve.sun.com/pub-cgi/show.pl?target=patchpage
|
Patches
|
Required patch 106300 does
not install.
|
This patch is a shared
library patch for 64-bit C++. The package SUNWlibCx is required on the
system. Install the SUNWlibCx package, or continue with patch
installation without installing patch 106300.
|
Startup
|
|
|
Nothing happens
|
No window appears when
launching Mozilla from a remote machine.
|
Set the DISPLAY environment
variable to your machine's display.
For example, "setenv DISPLAY <host name>:0.0"
|
Nothing happens
|
No
window appears
(You previously used Netscape 4.X)
|
Mozilla
1.7 for Solaris tries to migrate your Netscape 4.X preferences the
first time you launch Mozilla 1.7. A Netscape Communicator 4.X
preference may not have been migrated correctly, causing the error. Try
moving the ~/.mozilla directory to the ~/.mozilla.old directory. If
that does not work, try moving the ~/.netscape directory to the
~/.netscape.old, then restart the application.
|
Nothing happens
|
No window appears when
launched on
Solaris 2.6
|
Mozilla is not supported on
Solaris 2.6
Only on Solaris 8 and later
|
Wrong Browser
|
Mozilla starts up a Netscape
or FireFox window
|
Start Mozilla with a
parameter, for example "-P"
|
Error
|
On startup
Error message:
"Internal error: unavailable temporary resources."
|
Perform the following steps to increase the swap space
on your computer:
Solaris:
- Open a terminal window.
- Use the su command to switch to root.
- Type the following command: mkfile -v 100m
swapfile_name
- Type the following command: swap -a swapfile_name
Linux:
- Open a terminal window.
- Use the su command to switch to root.
- Type the following command: dd if=/dev/zero
of=/swapfile bs=1024 count=65536
- Type the following command: mkswap /swapfile
- Type the following command: swapon
/swapfile
|
Error
|
warning
message appears on the shell output: Gdk-WARNING **: shmat
failed!
|
This
message appears only if you run the mozilla -debug startup script. The
message indicates that there is not enough shared memory for the
application. The application still runs, but a little more slowly than
usual.
|
Display
|
|
|
Icons
|
Icons not displaying
correctly
|
Reset theme: View->Apply
Theme, Select any theme , then restart mozilla
|
Crash
|
|
|
Solaris 9v4
|
Crash
|
The gtk+-2.0 library on
Solaris 9 update 4 has a bug that causes the browser to crash.
Please get patch 115738-03 or higher to fix it.
|
Flash
|
Crashes when playing multiple
Flash Movies
|
Inside the system file (/etc/system) add the following
line
"set shmsys:shminfo_shmseg=your-number-here"
This will prevent crashes but the Flash files may still run slowly
|
Printing
|
|
|
Resize
|
Unable to print large page
with landscape format
|
1. Use scale only
2. Use Xprint system. About please refer to xprint.mozdev.org
|
Language
|
When printing non-western
web page, empty blocks will sometimes be printed instead of the
character.
|
Add search path for the
font: pref("font.directory.truetype.1", path)
the "prefs.js" file located in the ".mozilla" directory located in your
home directory.
|
Scripts
|
|
|
Javascript
|
Close window function does
not close tab
|
Change preferences setting
in prefs.js:
pref("dom.allow_scripts_to_close_windows", true);
|
Mail
|
|
|
IMAP
|
Some IMAP servers don't
support mixed type folders. So, a folder on this kind of server can
only store messages or sub-folders, but Mozilla mail supports mixed
folders as the default. So, this will cause some problems when creating
and deleting folders.
|
Open Edit->Mail
& Newsgroup Account Settings->Server Settings. Click "Advanced".
Uncheck "Server supports folders that contains sub-folders and
messages"
|
Profile
|
|
|
Loading
|
Crashes when loading profiles
(You have run a previous version of Mozilla)
|
The formats of some of the files in this directory have
changed, causing compatibility problems. To fix this problem, perform
the following steps:
- Open a terminal window.
- Type the following command: mv ~/.mozilla
~/.mozilla.old
- Restart the browser.
|
General
|
Mozilla is behaving
erratically
|
Profile corruption can cause
Mozilla to behave erratically. In this case create a new profile
|
Plugins
|
|
|
Java
|
Compatibility related problem
|
Please refer to
http://java.sun.com/j2se/1.5.0/compatibility.html to get more
information.
|
Chat
|
|
|
IP resolution
|
Unable to resolve server
address
|
Use IP address instead
|
Web Start
Uninstall
If you installed Mozilla 1.7 using Web Start run:
% cd <installation directory name>
% ./uninstaller
SVR4 Uninstall
If you installed Mozilla 1.7 from SVR4 packages (pkgadd
version), you should remove mozilla using pkgrm.
%pkgrm<installation package name>
Note: You must remove optional
packages separately and you must be logged in superuser
X-printing
How to set up x-printing for Mozilla.
Xprt is the Xprint print server for version
11 of the X Window system for non display devices such as printers and
fax machines.
Xprint is an advanced printing system which enables X11
applications
to use devices like printers, FAX or create documents in formats like
PostScript, PCL or PDF. It may be used by clients such as mozilla .
How do I configure Xprint on the client side?
There is an environment variable (env vars) which controls Xprint on
the client side.
The environment variable ${XPSERVERLIST} contains a list of display
identifiers
(separated by white space) to tell Mozilla where it can find the
X-print servers.
Example:
%export XPSERVERLIST="littlecat:80 bigdog:72"
This instructs an application to look at display 80 on the
machine"littlecat" and display 72 on the machine bigdog, to look for
X-print servers.
How do I setup an Xprint Server?
On Solaris Xprint Server is installed by default.
Xprt [ -ac ] [ -audit level ] [ -pn ] [ -fp fontpath
] [ -XpFile file ] [ -XpSpoolerType spoolername
] [ : display ]
: display
The X server runs on the given display. If multiple X servers
are
to run simultaneously on a host, each must have a unique display
number. Note that the standard X server (for video displays) typically
runs on display :0
Example: To start an Xprint Server on display
99:
%Xprt :99
-fp fontpath
sets the search path for fonts. This path is a comma separated
list of directories which Xprt searches for font databases.
Example:
%Xprt :99 -fp \
/usr/X/lib/X11/fonts/TrueType/,\
/usr/X/lib/locale/zh/X11/fonts/TrueType/ &
For more information about how to setup an Xprint Server,
please refer to http://xprint.mozdev.org/docs/Xprt.html
or refer to the man page ( "man Xprt" command on Solaris )
How to print web pages with
non-western fonts from Mozilla.
Pages containing non-western fonts may not
always print correctly, using TrueType printing will solve this problem.
What's TrueType printing?
Mozilla uses the FreeType library to translate True Type
fonts into
CID type 1 fonts. It then embeds the CID Type 1 font into the
postscript file.
How to set up TrueType printing?
TrueType printing is disabled by default. It can be enabled
by setting preferences in the all.js file located at greprefs/all.js as
following.
1. Set the preference "font.FreeType2.printing" to true.
Please note this feature requires freetype2 library support.
2. Set the preference "font.FreeType2.shared-library" to your
freetype library path.
The paths for each font set also need to be in the all.js file
You can add a path to search for new True Type fonts to the
all.js file.
Below are the default settings
pref("font.directory.truetype.1",
"/usr/X/lib/locale/zh/X11/fonts/TrueType");
pref("font.directory.truetype.2",
"/usr/X/lib/locale/zh.GBK/X11/fonts/TrueType");
pref("font.directory.truetype.3",
"/usr/X/lib/locale/zh_CN.EUC/X11/fonts/TrueType");
pref("font.directory.truetype.4",
"/usr/X/lib/locale/zh_CN.GB18030/X11/fonts/TrueType");
pref("font.directory.truetype.5",
"/usr/X/lib/locale/zh_TW/X11/fonts/TrueType");
pref("font.directory.truetype.6",
"/usr/X/lib/locale/zh_TW.BIG5/X11/fonts/TT");
To add a new font path use the same format:
pref("font.directory.truetype.<number>", "<path/
folder location>");
I.E. for Korean
pref("font.directory.truetype.7", "/usr/X/lib/locale/ko/X11/fonts/TrueType
");
What to do if Mozilla crashes
If Mozilla crashes you can take the following steps to assist
us debug.
Only Sun Mozilla version 1.4 & above can do this.
Mozilla version 1.2 and the community version cannot.
What is the core dump file?
The core dump file contains all the process information pertinent to
debugging: contents of hardware registers, process status, and process
data.
Where can I find it?
When a process crashes, the operating system writes out a core image to
a file (called a core dump) . Usually the core dump file is written to
the directory from which Mozilla was launched (provided it can be;
normal access controls apply).
Why can't the core dump file be written?
There are two possibilities:
1. The process does not have write permission to the
directory from which Mozilla was launched
Solution: Launch Mozilla from a directory
in which you have write permission.
2. The core dump file exceeds the default permitted maximum
size.
Solution: Remove the file size limit
using: 'ulimit -c unlimited'.
What should I do with the core file?
Send it to us directly at mozillafeedback@sun.com or let us know where we can get it. Be
sure to include your complete platform information.
You can get the complete information through: 'uname -a'
If it is hard to send the
core file, you can examine the file and send us the results.
Solaris has the following tools that can be used to examine the core
file:
/usr/bin/pstack ./core
/usr/bin/pmap ./core
/usr/bin/pldd ./core
Send the output in plain text format to mozillafeedback@sun.com
Mozilla - debug option
While
it has limitations, running Mozilla with the debug switch may be
helpful to administrators in diagnosing problems. Some error/warning
messages which do not show in normal mode will be displayed in two
scripts: debuginfo.sh and checkpatches.sh
will run if you launch mozilla with '-debug'. debuginfo.sh
prints out some system info and checkpatches.sh
checks if all the patches mozilla needed have been installed.
Example:
bash-2.03$ /usr/sfw/bin/mozilla -debug
------- Running Mozilla 1.7 debug mode-------
USER: work
HOSTNAME: eri0 = overhead
IP ADDRESS: eri0 = 129.158.217.54
ARCH: sparc
FRAME BUFFER(S): unknown
SunOS RELEASE: 5.8
KERNEL ID: Generic_108528-22
MEMORY: 512MB
SWAP: 879.0MB total, 374.6MB used, 504.3MB available
LOAD AVERAGE: 0.07, 0.02, 0.03
DNS DOMAINNAME:
ETHERNET ADDRESS: 0:3:ba:d:b8:f0
HOSTID: 830db8f0
Checking for recommended patches 108652-66 108921-16 112003-03
108773-18 111310-01 112472-01 108714-07 111111-03 112396-02 108940-54
108987-13 108528-22 108989-02 110380-04 110934-10 109147-24 111308-03
112438-01 110386-03 111023-02 108993-22 108434-14 108435-14 109159-03
109704-03 111721-04 113261-02 114542-01...
The following patches were not detected on this system:
114542-01 or higher
113261-02 or higher
111721-04 or higher
109704-03 or higher
109159-03 or higher
108435-14 or higher
108434-14 or higher
108714-07 or higher
112003-03 or higher
You may need to install the missing patch(es) on this system.
NOTE: The patch list above was created on Dec. 09, 2004 and a full patch
bundle is available on the Mozilla 1.7 for the Solaris OS download site.
Certain patches may have been updated since that date. For best
performance, we recommend that you use the patch bundle available with
the
product download, rather than pulling those patches (or patch updates)
individually from sunsolve.sun.com.
Please refer to the Mozilla 1.7 for the Solaris OS installation
documentation for more information. The document is available at:
http://www.sun.com/software/solaris/browser
.
Manually Implementing a
Profile Server
This
document assumes that you are implementing a Profile Server on a
dedicated server, rather than on an existing server. We recommend using
a dedicated Profile Server because it provides increased performance
and minimizes interaction with other applications. This document
provides instructions on how to implement Profile Server on either a
Java Enterprise Web Server (version 6.1 or later) or a Java Enterprise
Directory Server (versions 5.2). Since Profile Server does not rely on
any proprietary features of Java Enterprise servers, other servers may
work, but they have not been tested by Sun.
Which server type do I want to use?
You can store profile data on an HTTP, FTP or LDAP server. The server
type you choose is largely based on your existing infrastructure and
the need for administrative control over profile data. HTTP and FTP are
relatively easier to setup, but do not have all of the administration
features that LDAP has.
How do I Setup a HTTP Profile
Server?
Enable "Remote File Manipulation" for the HTTP Profile
Server.
- Start your Administration Server and navigate to the the
Administration Server page.
- Change to the "Class Manager" view.
- Click Content Mgmt tab.
- Choose "Remote File Manipulation" in the left pane.
- Check the Yes item below the label with "Activate file
manipulation commands".
- Apply the change.
Add rules for users of Profile Roaming
- Change to the "Server Manager" view.
- Click "Preferences" tab.
- Choose "Restrict Access" in the left pane.
- Edit the ACL file by adding access control rules
Note: be sure that the user has the
privilege to access their directory where roaming access files are
stored.
How do I setup a LDAP Profile
Server
-
Stop the Directory Server.
- Add the Profile Server schema, shown in listing below, to
your LDAP Server.
NOTE: Java Enterprise LDAP Server includes the schema by
default.
show
schema
#
ns-mcd-li-schema.conf
#
# Profile Server schema
#
|
attribute nsLIPtrURL
|
2.16.840.1.113730.3.1.399
|
ces
|
|
attribute nsLIPrefs
|
2.16.840.1.113730.3.1.400
|
ces
|
|
attribute nsLIProfileName
|
2.16.840.1.113730.3.1.401
|
cis
|
|
attribute nsLIData
|
2.16.840.1.113730.3.1.402
|
bin
|
|
attribute nsLIElementType
|
2.16.840.1.113730.3.1.403
|
cis
|
|
attribute nsLIServerType
|
2.16.840.1.113730.3.1.404
|
cis
|
|
attribute nsLIVersion
|
2.16.840.1.113730.3.1.405
|
integer
|
|
attribute nsServerPort
|
2.16.840.1.113730.3.1.280
|
cis
|
objectclass nsLIPtr
oid 2.16.840.1.113730.3.2.74
requires
objectclass
allows
nsLIPtrURL,
owner
objectclass nsLIProfile
oid 2.16.840.1.113730.3.2.75
requires
objectclass,
nsLIProfileName
allows
nsLIPrefs,
uid,
owner
objectclass nsLIProfileElement
oid 2.16.840.1.113730.3.2.76
requires
objectclass,
nsLIElementType
allows
owner,
nsLIData
nsLIVersion
objectclass nsLIServer
oid 2.16.840.1.113730.3.2.77
requires
objectclass,
serverhostname
allows
description,
cn,
nsServerPort,
nsLIServerType,
serverroot
- Restart the Directory Server.
- Create a root entry under which you will store the
profiles. You can store all the User Profiles under a single root entry
this simplifies the setup and management of Profile Roaming. The root
entry that you create can contain any object class, although you would
typically include the object class "orgazinationalUnit"
- Set access controls
for the root profiles entry, granting users both read and write access
to the entry and its sub nodes. Read access lets users copy their
profile data down to a local computer. In this way, you can use a
single access control rule to grant authenticated access to all users,
such as that shown in below.
Example:
(target="ldap:///ou=Roaming,o=mcom.com")(targetattr!="nsLIPrefs")(version
3.0; acl "Roaming"; allow (all) userdnattr ="owner"; )
- Depending on what server you're using, you might also be
able to set this ACL using a separate administrative tool.
- Under the profiles root, create a profile for each user by
creating a
nsLIProfile entry. Below shows an example of an LDIF that you can use
to create a profile entry for a user called pete.
Example:
dn: nsLIProfileName=pete,ou=Roaming,o=myCompany
changetype: add
objectclass: top
objectclass: nsLIProfile
nsLIProfileName: pete
owner: uid=pete,ou=People,o=myCompany
- Create user entries that Browser will authenticate users
against. You
can create new entries for users, as in listing below, or you can
replicate user entries from the corporate directory to the Profile
server (recommended).
Example:
dn: uid=pete,ou=People,o=myCompany
changetype: add
objectclass: top
objectclass: inetOrgPerson
cn: pete
userpassword: myPassword
Profile Roaming Preferences
Profile Server includes a set of new Browser
preferences that you can
use to control many aspects of the feature. For example, you can set or
lock preferences to enable the feature, set the location of the Profile
server or corporate directory, define what files users are permitted to
transfer to and from the server, and so on.
Profile Roaming preferences can be set in two places:
- On the Profile server, using Profile Server Control
- In Browser's Preferences window (set by the user)
The
browser stores all Profile Server preferences in special file:
"prefs.js" in the active user profile, along with other user
preferences that are served through Profile Server.
The
following table gives a full list of Profile Server preferences you can
set. Note that if you are setting preferences on the server using
Profile Server Control, you do not need to work with preferences
directly. Instead, you can use the graphical user interface of the
Profile Server Console.
Preference Setting
|
What file the preference lets you allow or
disallow to transfer.
|
|
|
roaming.files.abook.mab
|
Address book
|
roaming.files.history.mab
|
Collected address book
|
roaming.files.bookmarks.html
|
Bookmarks
|
roaming.files.cookies.txt
|
Cookies
|
roaming.files.hostperm.1
|
Cookie permissions
|
roaming.files.history.dat
|
Browser history
|
roaming.files.mimeTypes.rdf
|
Help Application Setting
|
roaming.files.panels.rdf
|
Sidebar panel list
|
roaming.files.localstore.rdf
|
Windows setting
|
roaming.files.liprefs.js
|
User preference
|
roaming.files.mailViews.dat
|
Mail view setting
|
roaming.files.training.dat
|
Junk mail filter
|
roaming.files.filter
|
Mail filters
|
|
Note: You can also use the
graphical user interface of the Profile Server Console.
|
Note: Some files have a tendency to become
large such as address book, browser history.
If the transfer of this file adversely affects network performance,
consider setting this preference to false on server side.
Advanced Features
Profile Server also supports the following features:
- Replication -
For greater performance and data integrity, Profile Roaming is
compatible with replicated LDAP servers. Simply point the Browser
client to a replicated server; writing to the master server is handled
automatically. (You can used the DNS round-robin technique to
distribute load across replicated servers)
- Server Side Preferences
- When reading a LDAP profile entry for Profile Roaming, The browser
can also pull down preferences set by an administrator in the nsLIPrefs
attribute
|