I noticed im getting some problems with ldap when its running and i reboot my linux box. before i reboot my box should i shutdown slapd using kill - INT processID or this is not an issue.
Regards,
Moe
Yahoo! Messenger with Voice. PC-to-Phone calls for ridiculously low rates.

I noticed im getting some problems with ldap when its running and i reboot my linux box. before i reboot my box should i shutdown slapd using kill - INT processID or this is not an issue.

The killall (from shutdown) will probably get it, but it might not
wait long enough for the process to finish flushing to disk.

You wait for the pid to go away before moving on with the shutdown.

5/15/06, Moe <moe_w90 (AT) yahoo (DOT) comwrote:
How do i ensure that everything is flushed to disk?

matthew sporleder <msporleder (AT) gmail (DOT) comwrote: I noticed im getting some problems with ldap when its running and i reboot my linux box. before i reboot my box should i shutdown slapd using kill - INT processID or this is not an issue.

The killall (from shutdown) will probably get it, but it might not
wait long enough for the process to finish flushing to disk.

5/16/06, John Madden <jmadden (AT) ivytech (DOT) eduwrote:
Mon, 2006-05-15 at 22:04 -0400, matthew sporleder wrote:
You wait for the pid to go away before moving on with the shutdown.

FWIW, the 'stop' stanza of my /etc/init.d/slapd is below. It sends a
-INT and keeps trying, preventing the box from going down until slapd's
done.

'stop')
if [ -f /var/run/slapd/slapd.pid ]
then
pid=`cat /var/run/slapd/slapd.pid`
res=`ps -efl | grep slapd | grep $pid`
if [ "$res" != "" ]
then
kill -INT `cat /var/run/slapd/slapd.pid`
echo "-INT sent to slapd"
sleep 1
res=`ps -efl | grep slapd | grep $pid`
while [ "$res" != "" ]
do
echo "slapd still running, waiting"
sleep 1
res=`ps -efl | grep slapd | grep $pid`
done
echo "slapd stopped"
else
echo "PID file found, but slapd not running"
fi
else
echo "slapd not running"
fi
;;
*)

This all really depends on your S vendor's implementation of
'shutdown' and/or 'init'. Since you're using linux, you can probably
look it up, but this goes beyond the scope of this list.

At 03:05 AM 5/16/2006, Moe wrote:
Can anyone please tell me what is /usr/bin/updatedb?.
man updatedb
updatedb is not part of LDAP Software. Further comment
on this list would be off-topic.
Kurt

5/16/06, Moe <moe_w90 (AT) yahoo (DOT) comwrote:
Hi,

Can anyone please tell me what is /usr/bin/updatedb?. I noticed high I wait on my linux box for quite some time and when i tracked the problem i found that the process for command /usr/bin/updatedb is in state D for a while. I believe it's related to Berkeley DB. Any suggestions

I think you may want to explore your man pages, especially those relating to:
'updatedb' and 'locate'

Moe said:
Hi,

Can anyone please tell me what is /usr/bin/updatedb?. I noticed high I
wait on my linux box for quite some time and when i tracked the problem
i found that the process for command /usr/bin/updatedb is in state D for
a while. I believe it's related to Berkeley DB. Any suggestions

It relates to the slocate command. updatedb scans the filesystem making a
database for slocate to speed its searches, and all the filesystem
grinding causes this i/o activity. Unless you use slocate or locate, you
might consider removing the slocate package as a hard solution.

Helpful hint: If you want to know what a command like this does, a couple
of useful ways to find info are:
* try doing a "man" on the command: "man updatedb"
* try finding out what package owns the file:
"rpm -qi /usr/bin/updatedb"

Alan Sparks, UNIX/Linux Systems Administrator <asparks (AT) doublesparks (DOT) net>