On Tue, Jan 21, 2014 at 10:11:16AM -0800, Gurucharan Shetty wrote:
> On Tue, Jan 21, 2014 at 10:04 AM, Ben Pfaff wrote:
> > On Tue, Jan 21, 2014 at 10:02:09AM -0800, Gurucharan Shetty wrote:
> >> On Tue, Jan 7, 2014 at 10:31 AM, Ben Pfaff wrote:
> >> > On Mon, Jan 06, 2014 at 02:40:34PM -0800, Gu
On Tue, Jan 21, 2014 at 10:04 AM, Ben Pfaff wrote:
> On Tue, Jan 21, 2014 at 10:02:09AM -0800, Gurucharan Shetty wrote:
>> On Tue, Jan 7, 2014 at 10:31 AM, Ben Pfaff wrote:
>> > On Mon, Jan 06, 2014 at 02:40:34PM -0800, Gurucharan Shetty wrote:
>> >> One option to implement openlog and syslog fun
On Tue, Jan 21, 2014 at 10:02:09AM -0800, Gurucharan Shetty wrote:
> On Tue, Jan 7, 2014 at 10:31 AM, Ben Pfaff wrote:
> > On Mon, Jan 06, 2014 at 02:40:34PM -0800, Gurucharan Shetty wrote:
> >> One option to implement openlog and syslog functionality in windows
> >> is to use windows event logger
On Tue, Jan 7, 2014 at 10:31 AM, Ben Pfaff wrote:
> On Mon, Jan 06, 2014 at 02:40:34PM -0800, Gurucharan Shetty wrote:
>> One option to implement openlog and syslog functionality in windows
>> is to use windows event logger. But it looks like it involves changing
>> registry settings and in genera
On Mon, Jan 06, 2014 at 02:40:34PM -0800, Gurucharan Shetty wrote:
> One option to implement openlog and syslog functionality in windows
> is to use windows event logger. But it looks like it involves changing
> registry settings and in general looks complicated.
>
> For the time being, do nothing
One option to implement openlog and syslog functionality in windows
is to use windows event logger. But it looks like it involves changing
registry settings and in general looks complicated.
For the time being, do nothing for syslog. All the information needed for
debugging will be present through
