8 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I copied the script from an AskUbuntu post -
#!/bin/bash
### BEGIN INIT INFO
# Provides: tomcat7
# Required-Start: $network
# Required-Stop: $network
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start/Stop Tomcat server
### END INIT INFO
... (14 Replies)
Discussion started by: Hijanoqu
14 Replies
2. UNIX for Dummies Questions & Answers
I want to install KDE on my Solaris PC , I downloaded solaris companion CD and question is there KDE available to install because I want that all my households work on one stable PC , but one condition is they must have K3B for burning files , and some GUI torrent program for downloading like Vuze... (2 Replies)
Discussion started by: solaris_user
2 Replies
3. Linux
I was wondering if someone here would happen to know how to setup a wireless connection with Fedora Core 4. I try to setup the internet options but my wireless adapter doesnt appear on the list... I'm new to fedora, and i never have setup a wireless connection with *nux systems. Any help, or... (5 Replies)
Discussion started by: kyoist
5 Replies
4. HP-UX
Can someone please point me in the correct direction for setting up a wireless card using HP-UX 11iV1? I know its different depending on the type of card I have, but im looking for a direction.
Thanks! (0 Replies)
Discussion started by: nickwinnie
0 Replies
5. UNIX Desktop Questions & Answers
Hi,
i want to start the X-Server without KDE or other Window Manager.
I need the X Server vor a Java Applikation!
Perhaps anybody can help me how to start it simply.
thanks
cu
Arne (6 Replies)
Discussion started by: hatzwatz
6 Replies
6. UNIX for Dummies Questions & Answers
Here is the story. I have some machines(RedHat 7.1 and RedHat 7.3) in an NIS domain. Ypserv and ypbind work alright, and I have logged onto different machines with the NIS accounts.
My problem arises when I try to start KDE with one of the NIS accounts. The error I get is that "there is no... (1 Reply)
Discussion started by: Jody
1 Replies
7. UNIX for Dummies Questions & Answers
Hi all,
I have a big problems here... In the install of FreeBSD 4.6, I've installed Kde3.0.0 . So, the file path is now : file:/root/.kde . And I want my user to access it... and maybe move it to another area (In the usr/local... because you know... my root directory isn't very tall...... (1 Reply)
Discussion started by: Erythro73
1 Replies
8. UNIX Desktop Questions & Answers
Hello, i,ve installed suse with kde 3.0, I had never used an X for unix before. So I don't know much.
Most things were easy to find, but what anoyes me a lot is that the desktop is larger than mij monitor, so I have to move my mouse to see the rest of the desktop.
I've tried to set the... (1 Reply)
Discussion started by: counTnegaTive
1 Replies
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)