Fonttastic

[god...@videotron.ca]

In etc/rc.d/rc0.d a link is found as K10fonttastic and points to
/etc/rc.d/init.d/fonttastic that does not exist. I beleive this is
causing errors' at start time to activate th fontfs daemon. Can anyone
point me in the rigth direction to correct this, if it is a problem.
Each time I start WP2000 a delay is encountered because of the
fonttastic server not being up.

Thanks

Paul Godin

[James Richard Tyrer]

"bi...@loves.you.com" wrote:

> In etc/rc.d/rc0.d a link is found as K10fonttastic and points to
> /etc/rc.d/init.d/fonttastic that does not exist.

This link should be there.

> I beleive this is
> causing errors' at start time to activate th fontfs daemon.

It is the fact that the script "/etc/rc.d/init.d/fonttastic" isn't there
that is causing the problem.

> Can anyone
> point me in the rigth direction to correct this, if it is a problem.
> Each time I start WP2000 a delay is encountered because of the
> fonttastic server not being up.

How long is this delay. Forever, perhaps :-).

Do you have FontTastic installed on your system?

Or if you think you installed it, how did you do it?

What distribution do you have?

JRT

[Robert Fargher]

bi...@loves.you.com wrote:

The files in the rcX.d directories are symbolically linked (ie.
soft-linked or symlink) to scripts in the init.d directories. Whether
init.d is /etc/init.d or /etc/rc.d/init.d is distribution dependent. Both
Mandrake 7.2 and Red Hat 7.0 are now making /etc/init.d are symlinked to
/etc/rc.d/init.d. If the fonttastic script is missing from init.d, you can
put it there, I think the original is in /usr/local/bin/fonttastic.

If it isn't there, you might (as root) run "updatedb". Once that has
finished (can take a while as it generates a searchable database of every
file on your system (you might want to unmount any CD you have mounted
first), you can search for the fonttastic script by "locate fonttastic".

On a more general note, you will have undoubtedly noticed that the rcX.d
directories contain files starting with S and others starting with K. The
S<number><name> files are processed upon entering that run-level (i.e.
rc3.d is for runlevel 3; rc5.d is for runlevel 5) by passing the "start"
parameter to the relevant script. Thus S80fonttastic is processed in
numerical order, after lower numbered S files, and starts up fonttastic.
The S files are startup files.

The K files are processed upon leaving that runlevel (perhaps to shutdown
or reboot) and are used to stop the various services. They pass the stop
paramter to the various scripts. So you can consider the K to stand for
"kill". :-)

Thus the K10fonttastic would not launch the font server.

Cheers,
Rob
Coast Mountain Linux Consulting