Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
It's probably something to do with ulimit. Maybe it's reached the maximum limit so it can't write to the log files anymore. But I thought the ulimit couldn't be set for the user root. I can't find anything about that in the man pages though so maybe it is possible. Try ulimit -a to see what all your limits are set to.
Originally posted by Mik Try ulimit -a to see what all your limits are set to.
core file size (blocks) 0
data seg size (kbytes) unlimited
file size (blocks) 100000
max locked memory (kbytes) unlimited
max memory size (kbytes) unlimited
open files 1024
pipe size (512 bytes) 8
stack size (kbytes) unlimited
cpu time (seconds) unlimited
max user processes 256
virtual memory (kbytes) unlimited
Nothing really obvious sticks out to me: do you see something?
Well syslogd most likely gets run as root so if that is root's ulimit then that would only happen if one of your log files is larger then a 100MB. But most likely you rotate your log files anyways so they would never get that big.
I don't know what else it could be, do your log files maybe give some more detailed info?
ok... i think i've found something. it has to do with the core file size...
i was reading about a old hacking method where a user would crash a program with root privledges, and use the core file output to gain root access. to prevent this, core file size is set to 0. i'm not sure about how secure it is to do this, but if you're not on a security critical system, try setting the core file size to 1024 or something, and see if that works.
i'll keep looking to see if i can find anything else.
Wow! It almost seems like a problem with the bash shell. I thought the "su - -s /bin/ksh" would check to see if a different shell would work, but now I'm wondering if it still goes through a bash shell before it invokes the korn shell. If it is bash, I don't understand why you can login from a console as root.
Do you have any problem su'ing to a generic user (who also uses bash)?
well... i don't have a solution, but i definitely admire the problem...
i sent a few messages to our mods in the security forum, so they should take a look at this thread as soon as they pop in. this is a pretty curious problem, so i'll keep looking around. let us know if you discover anything else.