08-04-2001
Run XF86Setup or Xconfigurator. Select custom form monitor list and give the correct value. Don't forget to backup existing Config file.
9 More Discussions You Might Find Interesting
1. Solaris
In order to use a regular PC monitor would I need to do any configuration changes to my Ultra 5 box running Solaris 8 ? (1 Reply)
Discussion started by: mangolinux
1 Replies
2. Shell Programming and Scripting
I am trying to monitor a log file and kick of a script when a change occurs. I know I could do this with a cron job and check for differences at set intervals, but I need the script to be dynamic and notify me as soon as there is a change in the log file. If anyone knows of a way to do this please... (1 Reply)
Discussion started by: goreb13
1 Replies
3. SCO
Is there command in sco unixware 7.1.3 from which i can find the temperature of the system/hardware.
Something equivalent to prtdiag in solaris maybe
thanks (1 Reply)
Discussion started by: gsb81
1 Replies
4. Shell Programming and Scripting
Hi ,
I have a configuration file which i have to monitor via a crontab.
Now i should be able to control the first cron job via a second one i start depending on the start time and stop time in config file.
say if the starttime is 10:00 AM and stop time is 12:00 Noon , i have to start the... (4 Replies)
Discussion started by: rvenkam
4 Replies
5. Shell Programming and Scripting
Hello,
I would like to write a script that use the display as an input.
In the display there is a list of file. I want to use it as an array and this would be the input in my script. Does somebody know how do I make it? (2 Replies)
Discussion started by: mig8
2 Replies
6. Hardware
Hi, I am experiencing troubles with dual monitors in fedora 16. During boot time both monitors are working, but when system starts one monitor automatically shut down. It happend out of the blue. Some time before when I updated system this happend but then I booted older kernel release and... (0 Replies)
Discussion started by: wakatana
0 Replies
7. Solaris
I recently had a Sun Ultra 45 shipped to me, when it was shipped it worked fine, but now I cannot get a display on the monitor. It did get a little banged up in shipping. I monitored the POST by connecting to the TTYa port and the only thing that looks like anything is wrong is:
Probing I/O... (1 Reply)
Discussion started by: Madrox72
1 Replies
8. Shell Programming and Scripting
Hi all,
i need to do the following,
when i connect to my website it prints out "Welcome User",
but sometimes there are errors like "dictionary not loaded" or "wrong user name or password"
so i wanted to make a script that checks that login page,
and if i get the Welcome massage do nothing,... (6 Replies)
Discussion started by: charli1
6 Replies
9. Infrastructure Monitoring
Sorry if this is the wrong forum
Searching for Saas Monitor service which monitor my servers which are sitting in different providers .
This monitor tool will take as less CPU as possible , and will send info about the server to main Dashboard.
The info I need is CPU / RAM / my servers status (... (1 Reply)
Discussion started by: umen
1 Replies
LEARN ABOUT CENTOS
kdeinit4
KDEINIT4(8) KDE User's Manual KDEINIT4(8)
NAME
kdeinit4 - KDE process launcher.
SYNOPSIS
kdeinit4 [--help] [[--no-fork] | [--no-kded] | [--suicide]] [[+programs] | [programs]]
DESCRIPTION
kdeinit4 is a process launcher somewhat similar to the famous init used for booting UNIX. It executes KDE programs and kdeinit loadable
modules (KLMs) starting them more efficiently.
Using kdeinit4 to launch KDE applications makes starting a typical KDE application a couple times faster and reduces memory consumption by
a substantial amount.
kdeinit4 is linked against all libraries a standard KDE application needs. With this technique, starting an application becomes much faster
because now only the application itself needs to be linked whereas otherwise both the application as well as all the libaries it uses need
to be linked.
DISADVANTAGES
The process name of applications started via kdeinit4 is "kdeinit4". This problem can be corrected to a degree by changing the application
name as shown by ps. However, applications like killall will only see kdeinit4 as the process name. To workaround this, use kdekillall
(from kdesdk/scripts) for applications started via kdeinit4.
OPTIONS
--help
Show help about options
--no-fork
Do not fork, i.e. do not exit until all the executed programs ends
--no-kded
Do not start kded
--suicide
Terminate when no KDE applications are left running
+programs
runs the programs handling requests
programs
runs the programs without handling requests
USAGE
A standard way to run this program is by simply specifying the following command at the prompt kdeinit4 program or kdeinit4 +program
FILES
/tmp/kde-$USER/kdeinit4_$INSTANCE
...
ENVIRONMENT VARIABLES
$HOME
Specifies the home directory of the current user
$KDE_HOME_READONLY
Specifies if the home directory of the current user is read only
$KDE_IS_PRELINKED
If set, tells kdeinit4 that the KDE programs are pre-linked.
(Prelinking is a process that allows you to speed up the process of dynamic linking.)
$KDE_DISPLAY
If set, tells kdeinit4 that it is running on a KDE desktop.
SEE ALSO
kded, kdekillall
BUGS
There are probably tons of bugs. Use bugs.kde.org[1] to report them.
AUTHORS
Waldo Bastian <bastian@kde.org>
Author.
Mario Weilguni <mweilguni@sime.com>
Author.
Lubos Lunak <l.lunak@kde.org>
Author.
NOTES
1. bugs.kde.org
http://bugs.kde.org
0.01.01 2008-10-03 KDEINIT4(8)