8 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
So I'm trying to search for the top 10 or 15 items under a directory by file type. I want to run a command on a directory and get something like the following:
Example of expected output.. .PDF: 100, .txt: 95, .word: 80..
What would be the best way of going about this? I've searched around... (2 Replies)
Discussion started by: shackle101
2 Replies
2. Shell Programming and Scripting
In the bash below I am trying to run the script entire script including the ....(which is a bunch of code) and then in the run function if the user response is y (line in bold). then start processing from execute function. Basically, goto the # extract folder for variable filename line and start... (4 Replies)
Discussion started by: cmccabe
4 Replies
3. Red Hat
Hi all
I am facing a problem.
I have configured SAMBA PDC on RHEL 6. Everything is going very smooth. Users are being logged in properly & their network drives (i-e; z: drives) are being shown. But either i login to Windows XP or Windows 7, user's profile does not get loaded. I get an error... (0 Replies)
Discussion started by: Yawar_Aziz
0 Replies
4. Red Hat
Hi All,
I am new to linux and i am configuring DNS server but while i restart service it shows below given error. Please help to solve this error.
# /etc/init.d/named restart
Stopping named:
Generating /etc/rndc.key:
... (2 Replies)
Discussion started by: Chintanghanti
2 Replies
5. Red Hat
I had a query that should the RHEL servers in production environment be re-started say every 2-3 months so that the cache is cleared?
I hope, my question is clear that should the Red Hat Linux servers be restarted periodically.
Please revert with the reply to my query.
Regards (17 Replies)
Discussion started by: RHCE
17 Replies
6. SuSE
Eclipse looks completely different when run under root compared to my user.
It's like kde wasn't setup for root upon installation.
I'm running Suse 9.3 Pro.
How do I configure root kde so that eclipse looks the same when run as user? (3 Replies)
Discussion started by: shwick2
3 Replies
7. Infrastructure Monitoring
Hello
I really wonder what's trap in etc/profile and in each user .profile.
I try to google for it but I think I have no luck. Mostly hit is SNMP traps which I think it is not the same thing.
I want to know ...
1. What's a "trap 2 3" means and are there any other value I can set... (4 Replies)
Discussion started by: Smith
4 Replies
8. Ubuntu
I posted this at another forum 25 minutes ago and it has only been looked at once. I have much more faith in this forum, as I've had some good help in the shell scripting forum.
So I'll just repost this here. I don't know if this is an (K)Ubuntu specific problem, but that is what I use. Problem... (0 Replies)
Discussion started by: notsomeone
0 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)