running mon as
Hi there Can I run mon as another user than root? Or is this necessary so? _ Behalten Sie Ihre Hotmails, den Messenger und die Suchfunktionen stets im Auge! http://toolbar.msn.ch?&DI=165&XAPID=2170 ___ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
Re: running mon as
On Mon, 2005-04-11 at 10:04 +0200, Anquijix Schiptara wrote: > Hi there > > Can I run mon as another user than root? Or is this necessary so? > > _ > Behalten Sie Ihre Hotmails, den Messenger und die Suchfunktionen stets im > Auge! http://toolbar.msn.ch?&DI=165&XAPID=2170 That's how I run it. So yes, it's possible ;p Ryan King ___ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
Re: Monitor output size limitation
On Fri, Apr 08, 2005 at 06:33:38PM -0700, Jim Trocki wrote: > On Fri, 8 Apr 2005, David Nolan wrote: > > > > >This is a known bug with some regexps in perl's Text::ParseWords that is > >tickled by large input from mon. > > well it's not really a bug, it's just that the default stack size is > inadequate for regexps in that module. bump up the stack allocation with > "uname -s" and you'll see the problem vanishes. I think you meant to say "ulimit -s" :-) ___ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
Re: Monitor output size limitation
On Mon, 11 Apr 2005, Ed Ravin wrote: On Fri, Apr 08, 2005 at 06:33:38PM -0700, Jim Trocki wrote: On Fri, 8 Apr 2005, David Nolan wrote: This is a known bug with some regexps in perl's Text::ParseWords that is tickled by large input from mon. well it's not really a bug, it's just that the default stack size is inadequate for regexps in that module. bump up the stack allocation with "uname -s" and you'll see the problem vanishes. I think you meant to say "ulimit -s" :-) yeah, one of those u.* commands. keep trying all of them until you find one that works :) ___ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
Socket-related prolem running mon on Solaris
Hi, I'm trying to run Mon on solaris (SunOS unified-ext 5.8 Generic_108528-13 sun4u sparc SUNW,UltraAX-e2) and keep getting the error Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/local/lib/perl5/5.8.0/sun4-solaris/Socket.pm line 373. which is caused by (I think) implicit calls to Sys::Syslog::setlogsock on log attempts. I just wanted to check whether this was a known problem (with a known fix) before scrambling around in the code... TIA, Alex -- Alex Hooper ___ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
Re: Socket-related prolem running mon on Solaris
On Mon, Apr 11, 2005 at 03:55:01PM +0100, Alex David Shadrach Hooper wrote:
> I'm trying to run Mon on solaris
> (SunOS unified-ext 5.8 Generic_108528-13 sun4u sparc SUNW,UltraAX-e2)
> and keep getting the error
>
> Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4
> at /usr/local/lib/perl5/5.8.0/sun4-solaris/Socket.pm line 373.
>
> which is caused by (I think) implicit calls to Sys::Syslog::setlogsock
> on log attempts. I just wanted to check whether this was a known
> problem (with a known fix) before scrambling around in the code...
What type of socket does Solaris use for syslog? Is it one of those
funky door things, a Unix domain socket, or a UDP socket? You might
want to start by playing with this code in Mon (line numbers approximate):
229
230 setlogsock('unix')
231 if grep /^ $^O $/xo, ("linux", "openbsd", "freebsd", "netbsd");
232
233 openlog ("mon", "cons,pid", $CF{"SYSLOG_FACILITY"});
And do something with the setlogsock() that's appropriate for Solaris
and/or the way you have syslog set up there.
If that doesn't help, write a quick sample program that sends a few log
entries using the example code in the man page for Sys::Syslog.
Does that reproduce the problem?
-- Ed
___
mon mailing list
mon@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/mon
Re: Socket-related prolem running mon on Solaris
Pulled from Ed Ravin's mail (Mon, Apr 11, 2005 at 11:21:59AM -0400):
>
> 229
> 230 setlogsock('unix')
> 231 if grep /^ $^O $/xo, ("linux", "openbsd", "freebsd", "netbsd");
> 232
> 233 openlog ("mon", "cons,pid", $CF{"SYSLOG_FACILITY"});
>
> And do something with the setlogsock() that's appropriate for Solaris
> and/or the way you have syslog set up there.
>
Ah, yes. I should have tried all the possibles listed in the Sys::Syslog
manpage before posting; 'stream' seems to work nicely. Thanks very much.
--
Alex Hooper
___
mon mailing list
mon@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/mon
