Jeremy:
Looks like I might have to eat my words a little. Not entirely on the running
of MySQL in a jail, but, perhaps that too, in time.
The application started as a knowledge-base, billing application.
The piece I'm concerned with now involves an implementation using
.profile/.bash_profile mechanisms and shell scripts that grab some environment
variables and set a few and inserts a record into a table that records the fact
that a particular user has logged into a remote workstation somewhere along with
version information, username, location, etc.
This environment remains until they logout/exit/crash, or someone kills them.
I've found the implementation trap "~/.logout" 0 has been pretty reliable in
ensuring an additional brother record with the same unique identifier gets
created, but, haven't researched how this mechanism has worked when terminals
crash/get killed.
This piece of the application is designed for auditing and tracking of
technician/end-user activities. It records how long technicians work on
particular client sites, also for billing and accountability purposes.
The goal is to get away from a cumbersome shell script/rc file implementation
and do the processing within a c binary.
The problem is the parent processes environment.
With what you've done in your chroot environment, have you found it possible to
replace the current environment with execvp, adding to it what you need, and,
having it work within that sub-process in a way that works without noticeable
differences to a shell without such enhancements? When it exits, are you able
to do any additional processing that might allow you to provide state and exit
status information from the exiting execvp?
If so, do you have some code examples I could examine?
TIA,
Van
--
=========================================================================
Linux rocks!!! http://www.dedserius.com
=========================================================================
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
