Does anyone know what the "touch /var/lock/subsys/dbora" line in the stock dbora does?
Printable View
Does anyone know what the "touch /var/lock/subsys/dbora" line in the stock dbora does?
i believe redhat checks that directory for running processes, and if there is one in there which matches your shutdown scripts it will call it.
Otherwise it won't - fair amount of stuff on google
Not sure I get it, so let me try to stick my foot in my mouth here...
The server starts and runs "dbora start",
which creates "/var/lock/subsys/dbora"
then dbora hangs for some reason (or what),
when the system is shutdown, it'll kill dbora?
Huh?
"touch" creates the dbora file. And the end has "rm -f /var/lock/subsys/dbora" to delete it.
stecal,
Sorry the question wasn't more succinct.
What's the purpose of creating this file? I think davey is on to it. But creating the file during startup or shutdown doesn't make sense to me.
From somewhere off the Internet:
The script creates a file in /var/lock/subsys to indicate that the subsystem or process is running, while the default script does not. As a background, the script /etc/rc.d/rc, when killing processes will execute all scripts for that runlevel that begin with a K, and it also checks if the subsystem is running by checking for the presence of a file, whose name must be similar, in /var/lock/subsys. Therefore, if you use the default script, it will not shutdown the database because of this missing file in /var/lock/subsys.
Maybe it's me. But if dbora is run during a startup, you don't want to kill any processes. If dbora is run during a shutdown, dbora (and dbshut) will stop all the oracle processes, right?
Sorry I don't get it.