Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
You should read this http://slack-linux.blogspot.com.au/2...ate-codes.html, but fundamentally, you need to look at the src for 'rwrun' and figure out the fundamental problem.
Killing processes like that won't solve anything in the long run and may lead to loss of data/functionality.
Thanks Chris....but i'm a bit confused. I ran ps -ef|grep rwrun and below is the output; Can i kill these processes? what could be the implication? Thanks a lot for your suppot.
on the first line.
Like I said, you need to find out what that prog does and how/why.
I repeat; randomly killing processes is nearly always the wrong to thing to do and may damage your system and/or data....
If it's "sleeping," then it can't be using 100% CPU, now can it?
These processes appear to be "part of Oracle." [i]Touch Not!![i]
If a process that's "part of Oracle" is really-busy and is consuming all the CPU it can get its hands on, I suggest that you should presume that it knows what it's doing.
Use Oracle-provided commands to find out what Oracle thinks it's doing, and use Oracle-provided commands to stop anything. Keep your "superduper powers" firmly in your pockets, unused.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.