No local.conf in /etc/fonts

trying to get additioanl fonts and making everything look great but no local.conf in the above location!!
Where did it go, how do I generate a new one, or do I have to write it from scratch?

OK....now you confused me. is Locale.conf just a simulink to another file/location? I just pacmaned ttf and would like to utilize them. On top of this, there are a couple of modifications to the above file that are recommended for LCD monitors to reduce fuzziness.
Should there be a general unmodified version to work from, or is it written from scratch?

Similar Messages

[SOLVED] I have no /etc/fonts/local.config

Hello,
in a Begginers guide here it is said that fontconfig application has all the global settings stored in a file
/etc/fonts/local.conf. But i don't have this file. In that folder i only have a file named fonts.conf.
I wonder if i found a typo in Arch Wiki? If not, why don't i have locals.config? Can i create it on my own?
Last edited by 71GA (2012-09-20 20:36:02)

When I click on your "here" link I get a page that says "Fontconfig configuration" and then "There is currently no text in this page. You can search for this page title in other pages, or search the related logs."
What am I missing?
Did you mean this page: https://wiki.archlinux.org/index.php/Font_Configuration ?
Did you look at /etc/fonts/fonts.conf? It says
DO NOT EDIT THIS FILE.
IT WILL BE REPLACED WHEN FONTCONFIG IS UPDATED.
LOCAL CHANGES BELONG IN 'local.conf'.
And if you follow the link to the fonts.conf man page you will see that it is set up to ignore a missing local.conf. You can create one if you like, but it would be better to put your changes in your user directory.
(edit) DSpider is right -- the files are local.conf and fonts.conf, not '.config'
Last edited by 2ManyDogs (2012-09-20 19:32:32)

[Solved] I make mistake, switch /etc/fonts/conf.d of ubuntu to my arch

Arch's fonts was too small in firefox and sites was difficult to read and with layout wrong because of font, then I switch the fonts config of ubuntu to my arch to fix this problem and I solve, otherwise now I receive errors in terminal when I perform a program like this: Fontconfig warning: "/etc/fonts/conf.d/53-monospace-lcd-filter.conf", line 17: invalid constant used : legacy".
somebody can help me?
sorry by bad english.
Last edited by solanoalves (2008-01-23 04:08:29)

A good idea would be to post that file.
An alternative would be to remove the contents of /etc/fonts/conf.d and reinstall the fontconfig package. Then follow the instructions in the wiki to get a better font rendering.
Good luck

Cannot set locale (ignored from /etc/locale.conf)

I just installed Arch on my new machine and I wrote:
==> /etc/locale.conf
LANG=es_CL.utf-8
# LANG=es_CL.UTF-8 (I've tried with both).
after uncommenting it on /etc/locale.gen and running # locale-gen
(I basically followed every step in the wiki).
No matter what I do when I start any terminal, I found the locale commands output:
$ ~ locale
LANG=
LC_CTYPE="POSIX
LC_NUMERIC="POSIX"
LC_TIME="POSIX"
LC_COLLATE="POSIX"
LC_MONETARY="POSIX"
LC_MESSAGES="POSIX"
LC_PAPER="POSIX"
LC_NAME="POSIX"
LC_ADDRESS="POSIX"
LC_TELEPHONE="POSIX"
LC_MEASUREMENT="POSIX"
LC_IDENTIFICATION="POSIX"
LC_ALL=
I found that if I open a tty, the /etc/profile.d/locale.sh is ran so, the locales are correct and locale shows the correct output.
The weirdest thing is that my old machine doesn't load locale.sh, and still the locale it's right.
I've search a lot through the wiki and bbs and even when there are couple of articles, none of them help me to solve this issue :(.
I'm running my session through systemd --user (in case it means anything).
EDIT: Add more info.
EDIT2: Fix typo
Last edited by pablox (2013-03-25 13:19:42)

WorMzy wrote:
Looks like it is, I removed it from my .zshrc and nothing changed.
Could you check whether es_CL.UTF-8 is actually listed as an available locale?
localectl list-locales
And if so, whether it's correctly set
localectl status
$ localectl list-locales
en_US.utf8
es_CL.utf8
$ localectl status
System Locale: LANG=es_CL.UTF-8
LC_COLLATE=C
LC_MESSAGES=C
VC Keymap: la-latin1
X11 Layout: n/a
$ locale
LANG=
LC_CTYPE="POSIX"
LC_NUMERIC="POSIX"
LC_TIME="POSIX"
LC_COLLATE="POSIX"
LC_MONETARY="POSIX"
LC_MESSAGES="POSIX"
LC_PAPER="POSIX"
LC_NAME="POSIX"
LC_ADDRESS="POSIX"
LC_TELEPHONE="POSIX"
LC_MEASUREMENT="POSIX"
LC_IDENTIFICATION="POSIX"
LC_ALL=
$
Ô_o
I have removed an empty ~/.zprofile just in case but the issue persist. Running an empty zsh shell (with zsh -f) doesn't work either.
Last edited by pablox (2013-03-26 23:59:45)

What should I set up in locale.conf to avoid conversion errors?

When I try to use my Ruby script I always get a "invalid byte sequence in US-ASCII (ArgumentError) exception". I managed to track down that program arguments are passed in US-ASCII encoding. However Ruby scripts are using strings with UTF-8 encoding. Formerly those Ruby scripts worked fine, and I found out they keep working if I explicitly convert program arguments (passed as ARGV[]) to UTF-8 encoding.
I think I have "locale" problems. Maybe I should set up LC_CTYPE somewhere in the config files.
When I issue command "locale -a" I see:
C
POSIX
en_US.utf8
hu_HU.utf8
/etc/locale.conf
LANG=en_EN.UTF-8
LANGUAGE=en_EN.UTF-8
LC_CTYPE=en_EN.UTF-8
However I added the last line recently, and I don't know how to "source" this kind of file, to manifest their content.

As far as I know, the locale / LANG setting en_EN.* does not exist, at least it does not appear in my /etc/locale.gen.
You probably want en_{US,GB}.UTF-8 (or anything else from /etc/locale.gen)
Though, I am not sure whether this is related to your problem, since 'locale -a' gives correct output.
Last edited by respiranto (2015-06-02 20:18:07)

Lots of fonts messed up. /etc/fonts/ dissapeared :s

I started up arch today and went to open something in mousepad, i noticed that monospace was messed up so i ran "fc-cache -fv" as root and normal user again. Then rebooted now there are more fonts that have messed up like sans etc.
Anyone know how to fix this? Here's the output of fc-cache.
[ash@breakage ~]$ fc-cache -fv
Fontconfig error: Cannot load default config file
/usr/share/fonts: caching, new cache contents: 0 fonts, 10 dirs
/usr/share/fonts/100dpi: caching, new cache contents: 398 fonts, 0 dirs
/usr/share/fonts/75dpi: caching, new cache contents: 398 fonts, 0 dirs
/usr/share/fonts/TTF: caching, new cache contents: 62 fonts, 0 dirs
/usr/share/fonts/Type1: caching, new cache contents: 35 fonts, 0 dirs
/usr/share/fonts/artwiz-fonts: caching, new cache contents: 16 fonts, 0 dirs
/usr/share/fonts/cyrillic: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/encodings: caching, new cache contents: 0 fonts, 1 dirs
/usr/share/fonts/encodings/large: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/local: caching, new cache contents: 26 fonts, 0 dirs
/usr/share/fonts/misc: caching, new cache contents: 55 fonts, 0 dirs
/usr/share/fonts/util: caching, new cache contents: 0 fonts, 0 dirs
/var/cache/fontconfig: not cleaning unwritable cache directory
fc-cache: succeeded
I also noticed on starting up arch it gives an error something like "unable to load default font"
Edit: Also just noticed that the /etc/fonts/ folder has dissapeared.
Last edited by Breakage (2008-02-17 18:36:36)

Thanks fwojciec, just worked that out seconds before thanks for the reply though man.
It worked too, strange that the whole folder just disappeared.
Last edited by Breakage (2008-02-17 18:37:12)

System ignore locale.conf

hi to everybody,
I have a very annoying problem:
setting up LANG via /etc/locale.conf (because I want system-wide configuration) is ignored
while setting up via ~/.bashrc works ...
this is what I get, without
export LANG=en_GB.UTF-8
in the ~/.bashrc, but with
LANG="en_GB.UTF-8"
in my /etc/locale.conf
[mattia@arch-dekstop ~]$ locale -a
C
POSIX
en_GB.utf8
[mattia@arch-dekstop ~]$ locale
LANG=
LC_CTYPE="POSIX"
LC_NUMERIC="POSIX"
LC_TIME="POSIX"
LC_COLLATE="POSIX"
LC_MONETARY="POSIX"
LC_MESSAGES="POSIX"
LC_PAPER="POSIX"
LC_NAME="POSIX"
LC_ADDRESS="POSIX"
LC_TELEPHONE="POSIX"
LC_MEASUREMENT="POSIX"
LC_IDENTIFICATION="POSIX"
LC_ALL=
instead with it in my ~/.bashrc, I get:
[mattia@arch-dekstop ~]$ locale -a
C
en_GB.utf8
POSIX
[mattia@arch-dekstop ~]$ locale
LANG=en_GB.UTF-8
LC_CTYPE="en_GB.UTF-8"
LC_NUMERIC="en_GB.UTF-8"
LC_TIME="en_GB.UTF-8"
LC_COLLATE="en_GB.UTF-8"
LC_MONETARY="en_GB.UTF-8"
LC_MESSAGES="en_GB.UTF-8"
LC_PAPER="en_GB.UTF-8"
LC_NAME="en_GB.UTF-8"
LC_ADDRESS="en_GB.UTF-8"
LC_TELEPHONE="en_GB.UTF-8"
LC_MEASUREMENT="en_GB.UTF-8"
LC_IDENTIFICATION="en_GB.UTF-8"
LC_ALL=

I found two similar threads:
https://bbs.archlinux.org/viewtopic.php … 1#p1252841
https://bbs.archlinux.org/viewtopic.php … 5#p1153155
Both blame incorrect sourcing /etc/profile
What's the output of 'localectl list-locales' and 'localectl status'?

KDE and locale.conf

Since last two months I've been having weird issue with KDE, special characters in files don't display correctly.
I've upgraded my configuration files as it was told here
Now, my locale.conf looks like that:
LANG="pl_PL.UTF-8"
LC_MESSAGES=C
It is working ok when I'm logged on terminal, but in KDE session locale command gives me:
LANG=
LC_CTYPE="POSIX"
LC_NUMERIC="POSIX"
LC_TIME="POSIX"
LC_COLLATE="POSIX"
LC_MONETARY="POSIX"
LC_MESSAGES="POSIX"
LC_PAPER="POSIX"
LC_NAME="POSIX"
LC_ADDRESS="POSIX"
LC_TELEPHONE="POSIX"
LC_MEASUREMENT="POSIX"
LC_IDENTIFICATION="POSIX"
LC_ALL=
I'm not sure why, but KDE does not inherit locale settings, any idea what am I doing wrong?

Maybe KDE takes the settings from rc.conf rather than locale.conf? I don't have the latter at all and it seems to pick up the settings from rc.conf so that I get LANG set en_GB.UTF-8 and everything else as C (since DAEMON_LOCALE is set to no in rc.conf).
It definitely doesn't pick some of the locale stuff up, though, since it doesn't show the other generated locales in system preferences...

How do I change my computors address..eg: it keeps showing my location as Herndon,Va on my local search, weather etc:..Im in Florida

How do I change my computer address...eg: It keeps showing my location as Herndon, Va on my local search, weather etc: when my actual location is in Orange City, Fla. This just began fairly recently (the past month) Thank you for your help!

Where does this web page say you are located?
http://whatismyipaddress.com/

[SOLVED] Fontconfig warning: "local.conf"

Hello Folks,
every software I run from the terminal shows me a long list of the same message, before to run.
Here an example:
skype
Fontconfig error: "local.conf", line 82: invalid attribute 'target'
Fontconfig error: "local.conf", line 85: invalid attribute 'target'
Fontconfig warning: "local.conf", line 181: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 194: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 213: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 229: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 291: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 426: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 530: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 544: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 558: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 614: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 628: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig error: "local.conf", line 635: invalid attribute 'name'
Fontconfig warning: "local.conf", line 229: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 291: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 426: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 530: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 544: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 558: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 614: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 628: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig error: "local.conf", line 635: invalid attribute 'name'
Fontconfig warning: "local.conf", line 642: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 656: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig error: "local.conf", line 663: invalid attribute 'name'
Fontconfig error: "local.conf", line 687: invalid attribute 'name'
Fontconfig error: "local.conf", line 706: invalid attribute 'name'
Fontconfig error: "local.conf", line 730: invalid attribute 'name'
Fontconfig warning: "local.conf", line 742: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig error: "local.conf", line 749: invalid attribute 'name'
Fontconfig warning: "local.conf", line 756: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig error: "local.conf", line 776: invalid attribute 'name'
Fontconfig warning: "local.conf", line 799: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig error: "local.conf", line 806: invalid attribute 'name'
Fontconfig warning: "local.conf", line 813: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig error: "local.conf", line 833: invalid attribute 'name'
Fontconfig error: "local.conf", line 879: invalid attribute 'name'
Fontconfig warning: "local.conf", line 903: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 916: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 931: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 943: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 959: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig error: "local.conf", line 966: invalid attribute 'name'
Fontconfig warning: "local.conf", line 973: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig error: "local.conf", line 992: invalid attribute 'name'
Fontconfig error: "local.conf", line 1009: invalid attribute 'name'
Fontconfig error: "local.conf", line 1026: invalid attribute 'name'
Fontconfig warning: "local.conf", line 1290: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig error: "local.conf", line 1293: invalid attribute 'target'
Fontconfig warning: "local.conf", line 1316: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 1524: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig error: "local.conf", line 1527: invalid attribute 'target'
Fontconfig warning: "local.conf", line 1537: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 1654: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 1871: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 1905: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 1937: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 1985: Having multiple values in <test> isn't supported and may not work as expected
How could I solve it?
Last edited by Astroarch (2014-09-11 17:56:30)

Then , I solved deleting the file and reinstalling fontconfig.
Byt he way, I do not post in the forum to be joked, if you mean to answer in such a way, better do not post at all.
Thanks
Last edited by Astroarch (2014-09-11 17:56:07)

Assistance with font configuration /etc/fonts/local.conf

Hello,
I would like to replace all non-monospace fonts with Semplice Regular, size 6px, and all Monospace fonts with Profont, size 8.
After messing around with the configuration for two days, I have come to a sad realization that I have no clue.
In particular, these lines of code amaze me the most:
<match target="pattern" name="family">
<test name="family" qual="any" compare="not_eq" >
<string>monospace</string>
</test>
<edit mode="assign" name="family" >
<string>Semplice Regular</string>
</edit>
</match>
I would expect that it would replace all-monospace with Semplice Regular, leaving the size unmodified for now as I was trying to get at least something working. However, what it does, is that it makes me unable to use almost all fonts and replaces those with a generic one.
Could someone enlighten me on the matter? Thank you!
fc-list
Semplice Regular:style=Regular
Last edited by KSiimson (2008-09-15 16:19:28)

Your rule might need "fixed" instead of, or as well as, "monospace".

Pacman.conf.pacsave etc?

I recently upgraded my system to the newer packages and I noticed some messages when I did this. The pacman.conf.save as well as rc.local.pacsave and a few others were listed as being created. What wasn't clear was what I am supposed to do with these multiple files.
I noticed that the pacman.conf file was actually different than my original as the IGNOREPKG line was commented whereas I had mine commented out.
So, can this be clarified? Perhaps even a list of the files that typically get replaced and what users are supposed to do with them.
Thanks in advance.

Anything with a .pacsave extension is a configuration file that has been backed up. Your previous pacman.conf file was moved to /etc/pacman.conf.pacsave and the new file from the new package was placed in as /etc/pacman.conf.
To prevent that from happening, add etc/pacman.conf to one of the NoUpgrade lines in pacman.conf. Then the next time pacman is upgraded, your original config will be preserved and the new file will be saved as /etc/pacman.conf.pacnew.

Hi accidentally overwrote new pacman.conf with /etc/pacman.conf.pacnew

Hi
I accidentally overwrote etc/pacman.conf with the old /etc/pacman.conf.pacnew.
Pacman now appears to work but disregards the signing of packages.
Is there an copy of the pacman.conf from the upgrade around so I can merge
the two files. perhaps pacman.conf~, but no I think this is overwritten too.
Regardz
El Zorro

Hi Trilby,
it may be the mouldy oldy one as there is no reference to "SigLevel = Never" it does not seem to exist only "Architecture = auto"
Here is the current /etc/pacman.conf
# /etc/pacman.conf
# See the pacman.conf(5) manpage for option and repository directives
# GENERAL OPTIONS
[options]
# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
#RootDir = /
#DBPath = /var/lib/pacman/
#CacheDir = /var/cache/pacman/pkg/
#LogFile = /var/log/pacman.log
HoldPkg = pacman glibc
# If upgrades are available for these packages they will be asked for first
SyncFirst = pacman
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#XferCommand = /usr/bin/curl -C - -f %u > %o
#CleanMethod = KeepInstalled
Architecture = auto
# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
#IgnorePkg =
#IgnoreGroup =
#NoUpgrade =
#NoExtract =
# Misc options (all disabled by default)
#UseSyslog
#ShowSize
#UseDelta
#TotalDownload
#CheckSpace
# REPOSITORIES
# - can be defined here or included from another file
# - pacman will search repositories in the order defined here
# - local/custom mirrors can be added here or in separate files
# - repositories listed first will take precedence when packages
# have identical names, regardless of version number
# - URLs will have $repo replaced by the name of the current repo
# - URLs will have $arch replaced by the name of the architecture
# Repository entries are of the format:
# [repo-name]
# Server = ServerName
# Include = IncludePath
# The header [repo-name] is crucial - it must be present and
# uncommented to enable the repo.
# The testing repositories are disabled by default. To enable, uncomment the
# repo name header and Include lines. You can add preferred servers immediately
# after the header, and they will be used before the default mirrors.
#[testing]
#Include = /etc/pacman.d/mirrorlist
[core]
Include = /etc/pacman.d/mirrorlist
[extra]
Include = /etc/pacman.d/mirrorlist
#[community-testing]
#Include = /etc/pacman.d/mirrorlist
[community]
Include = /etc/pacman.d/mirrorlist
# An example of a custom package repository. See the pacman manpage for
# tips on creating your own repositories.
#[custom]
#Server = file:///home/custompkgs
Trilby wrote:
The pacnew version includes everything for package signing. All you will have lost is any personal changes you have made.
The package signing lines are, however, commented out except for the "SigLevel = Never" line. Just read the instructions within the comments and uncomment the appropriate SigLevel line (and comment the "Never" line).
Last edited by elzorro (2012-01-21 06:31:50)

Setting global umask via NSUmask or /etc/launchd.conf and /etc/launchd-user.conf broken?

The procedure to change the default global umask from 0022 to 0002, so that most files created by one user on a machine will be read-write by other users in the same group, seems to have been broken or to have been changed in OS X Lion from OS X Snow Leopard. What worked as far back as OS X 10.4 and was officially documented was done from Terminal: "defaults write /Library/Preferences/.GlobalPreferences NSUmask 2" (with a sudo, if not logged in as 'root').
Another way documented in various places and which I actually used through OS X 10.6 was also done via Terminal. Two files were created: /etc/launchd.conf (for system-wide global umask) or /etc/launchd-user.conf (for user-specific global umask). The contents of each were simply the single umask command, "umask 002" or ("umask u=rwx,g=rwx,o=rx", I can't remember which variant I used - they're functionally the same, though).
No matter which method I use, the 2nd or the 1st, the global umask no longer changes.
Does anyone know whether this has been deliberately hobbled under OS X Lion, requiring purchase of OS X Lion Server? Is this an OS X Lion bug? Or, am I looking at something wrong?

See this support article, which was written for OS X Server, but seems applicable to Mac OS X client versions as well:
Mac OS X Server v10.5, 10.6: Setting a custom umask
The excerpt below describes the use of /etc/launchd-user.conf, and strongly cautions against using /etc/launchd.conf.
Umask for user applications
In Mac OS X v10.5.3 and later, you can create the file /etc/launchd-user.conf with the contents "umask nnn". Do not include the quotation marks and replace nnn with the desired umask value, such as 027 or 002.
This will set the user's umask for all applications they launch, such as Finder, TextEdit, or Final Cut Pro, and control the permissions set on new files created by any of these applications.
Umask for system processes
In Mac OS X v10.4 and later, create the file /etc/launchd.conf with the contents "umask nnn". Do not include the quotation marks and replace nnn with the desired umask value, such as 027 or 002.
This will set the umask for all processes. Changing this value is strongly discouraged because it changes the permissions on files used by the system software. If the permissions are too restrictive, dependent software may not work. If the permissions are too open, they may introduce security issues.

Clusterware confused in /etc/ocfs.conf or /etc/ocfs2/cluster.conf

Hello,
This is very surprising sitaution . I installed ocfs2 ,when I finished installing clusterware it is asking for /etc/ocfs.conf and integrity check is failing.
OS RHEL 4 64 bit
ORACLE 10.2
anyone have clue that why clusterware is behaving like this?
Thanks,
S.Mann

More info...
I installed OCFS2 and when I check the inetgrity
the result is this
sh runcluvfy.sh comp cfs -n node1,node2 -f /u21
Verifying CFS integrity
Checking CFS integrity...
Checking existence of "/etc/ocfs.conf" file...
File "/etc/ocfs.conf" does not exist on the following nodes:
node2
Existence check failed for file "/etc/ocfs.conf".
Checking host-guid uniqueness...
Uniqueness check for host-guid failed.
Checking required run level configuration for ocfs...
OCFS is configured with proper run level on all the nodes.
Checking shared storage accessibility...
"/u21" is not shared.
Shared storage check failed on nodes "node2,node1".
==============================
Why it is /etc/ocfs.conf as this is not the feature of OCFS2?

No local.conf in /etc/fonts

Similar Messages

Maybe you are looking for