Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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.
After shutting down the server, when I started it up, it didn't show the genome display and gave the following error:
Dec 19 18:23:47 demo gconfd (root-4278): starting (version 2.8.1), pid 4278 user root'
Dec 19 18:23:47 demo gconfd (root-4278): Bad permissions 777 on directory /tmp/gconfd-root
Dec 19 18:23:47 demo gconfd (root-4278): Failed to get lock for daemon, exiting:
Directory /tmp/gconfd-root has a problem, gconfd can't use it.
After deleting gconfd-root, it started up with GUI mode.My query is that it happens all the time when the server is restarted.Let me also tell you that there are two Oracle instances running in this server. Is this problem has to do with this fact?
Can anybody provide a solution on this issue so that this can be stopped from happening all the time?
May I know the location of the shutdown script where I can putdown the command to clean the /tmp directory?
Regards,
Kosys
I think that this is the way that you do it in Red Hat. There is a directory called /etc/rc0.d which holds all of the shutdown scripts. These shutdown scripts are run in order. Toward the end of the scripts is one that mounts / as read-only. You need to clean /tmp just before / is mounted as read-only. So try editing the script which mounts / as read-only and place these commands at the very beginning of the script:
# The following two commands were added by kosys to clean /tmp at shutdown
echo "cleaning /tmp"
rm /tmp/* -R
I'm quite new in system administration.........so a little more details will be of much help.....
As per your suggestion I checked out the scripts under /etc/rc0.d but could't found one that mounts / as readonly.
I'm giving the list of the scripts under /etc/rc0.d. Can you please check out(by the script name) and tell me which is the script that mounts / as readonly which I can edit to clean /tmp.
Can I manually delete all the files in /tmp before running shutdown command(instead of adding the removal command in the script under /etc/rc0.d)?
Yes, you can. The potential problem is that some daemon might need information in one of the files in /tmp and fail to shutdown properly. So the best thing to do is clean /tmp as late in the shutdown process as possible.
One of the last things that is done in shutdown is to mount / as read only to make sure that all write buffers are written out before shutdown. You can't delete anything after / is mounted read only so /tmp has to be cleaned before / is mounted read only.
Quote:
Originally Posted by kosys
....
As per your suggestion I checked out the scripts under /etc/rc0.d but could't found one that mounts / as readonly.
I'm giving the list of the scripts under /etc/rc0.d. Can you please check out(by the script name) and tell me which is the script that mounts / as readonly which I can edit to clean /tmp.
I don't have Red Hat installed so I can't look through the individual scripts. The scripts are run in alphabetical order and the one you are looking for should be very near the end. If you put the script after / is mounted read only then you will simply get an error message saying that you can't delete files on a read only file system. So I would try placing the commands at the beginning of S01halt. If that doesn't work try the beginning of S00killall, and so on.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.