04-04-2011
Quote:
Originally Posted by
theKbStockpiler
If init needs the fork command to start a new process
Init unlikely ever starts X clients. Init is a low level process. Clients are launched by X11 initialization scripts or later by user interaction with existing clients.
Quote:
, what is inbetween clicking a mouse button and starting the new process? Which alreadly occuring process issues the fork command?
That can be a window manager, a desktop environment component or whatever process.
This User Gave Thanks to jlliagre For This Post:
6 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi all,
There is an application which can be launched once on our box and there are several suspected users telnet into the system with the same login ID.
Is there a way that i can find out from which tty the application is launched? If so, i can get the user name from the "finger"... (1 Reply)
Discussion started by: sleepy_11
1 Replies
2. UNIX for Dummies Questions & Answers
Hello there,
I "discovered" an interesting command lastlog, but I couldn't find, until now:cool:, if it's possible to get a list of the launched process by users and root during a certain of time...
...any idea would be really appreciated!!!
Thanks in advance.
Giordano Bruno (3 Replies)
Discussion started by: Giordano Bruno
3 Replies
3. Shell Programming and Scripting
Hi All
I launch some application in a remote machine using ssh
EXAMPLE
ssh -X myname@mycompany@RemoteServerIp 'myApplicationName'
When I want to kill the application I hit CTRL+C and I see a message 'Killed by signal 2'. Unfortunately on the remote machine the application is not really... (1 Reply)
Discussion started by: manustone
1 Replies
4. Shell Programming and Scripting
I need to know how to have a BASH script run every time Firefox is launched, what is the simplest way to do this? (1 Reply)
Discussion started by: glev2005
1 Replies
5. Debian
Hi,
i use a crunchbang-LINUX . The Problem: When i download and save a picture, the system automaticaly launches gimp. i tried to find a config file, were i can switch of this "gimp-start," but unfortunatelly i didnt find it.
cat /etc/X11/default-display-manager
/usr/bin/slim
I'm also not... (2 Replies)
Discussion started by: IMPe
2 Replies
6. Shell Programming and Scripting
Hi Experts,
I am creating a script to monitor a certain applications running in my Unix system.
My script order goes this way:
df -h /of/a/filesystem
tail -5 /path/to/an/application/availability
su -c "jsmon pf=(profile of my application) `echo "p"`" usradm
#EOF
I am... (7 Replies)
Discussion started by: Xworks
7 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)