Hi VK,
On Sat, 2006-09-16 at 08:25 -0700, vivek kamat wrote:
> but my problem is, The menu based utility is, currently in use my
> production system and is working great..and and I just need to add a
> new "menu option" in the existing environment to start and stop my
> application. And I need to find the solution for my problem.
Okay.
> I wonder there is any built in utility in solaris which will create a
> log file to capture all menu options the user have executed for that
> day...however my current setting logs all the activities that are done
> from the menu by the user.
Why ? Is this for the server admin, or the user to consume ? If it's for
the server administrator, then I think the Solaris Auditing I pointed
to earlier will do this for you in a supported manner, but otherwise,
you could simply echo the menu item to a known file in each users' home
directory before invoking the application, remembering to periodically
empty this file.
> #!/usr/bin/ksh
> echo "$PASSWD" | nohup /export/home/application/bin/app_process1 &
> echo "$PASSWD" | nohup /export/home/application/bin/app_process2 &
>
Does nohup -p or -g fix this ? (does -a help ?) Sorry, a bit at a loss
as to what to suggest otherwise.
cheers,
tim
--
Tim Foster, Sun Microsystems Inc, Solaris Engineering Ops
http://blogs.sun.com/timf
