* Shawn Walker <[EMAIL PROTECTED]> [2008-06-26 03:34]:
> I'm in the process of implementing a solution for bug 2333
> (controlling access / error log destination).
> 
> Here's the one-email version:
> 
> It has been requested that the ability to control where access and error log
> information is sent be added to the depot server software.
> 
> This is so that administrators can reserve the smf logs for errors and send
> access information to a separate log file or /dev/null.
> 
> The basic idea here is to add a -l parameter that you could use to define 
> where
> to send the contents of each log file.
> 
> You would use thusly:
> 
> depot.py -l errors=destination -l access=destination
> 
> Where destination is stderr, stdout, or a filename (including /dev/null).
> 
> If you do not specify the -l option, or you do not specify one of the two log
> types it would default as such:
> 
> errors -> stderr
> access -> stdout
> 
> Two new SMF properties would be added: pkg/access_log and pkg/error_log,
> respectively.
> 
> Thoughts?

  Why not just use long options?  What other -l settings do you
  envision?  (I'm pretty sure that the -a auth=url approach was
  wrong--my fault--so it would be nice to understand why something
  similar is needed here.)

  - Stephen

-- 
[EMAIL PROTECTED]  http://blogs.sun.com/sch/
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to