[ale] Redirecting stderr on current shell

[James P. Kinney III]

Hmm. I would bet that the client is using the syslog.conf from the
mother server. But the client doesn't have a /var/log/messages file to
write to since it is a local process with only ram disks. 

You will likely need to look at one of the networked syslogs and some
nfs sharing to be able to keep a syslog from each of the nodes. 

Syslog.conf does have the ability to turn on/off errors to the
screen/console. The default is to write to the console if the file
location is not available for what ever reason. It should be possible to
turn the syslog reporting to be error or higher for everything from the
.conf file that is used to start syslog on the nodes. That way, critical
problems will appear but the general noise will not. 

On Wed, 2003-06-04 at 17:39, Christopher Fowler wrote:
> Syslogd might not be running?  Or, it is but can not open its 
> message file so it displays messages to console
> 
> On Wed, Jun 04, 2003 at 10:07:55AM -0400, John Wells wrote:
> > Guys,
> > 
> > We've been playing around with the knoppix cluster cd here at work and
> > have gotten a client booting up via PXE (which is very sweet, btw).
> > 
> > Anyway, when we get up to a shell on the client, syslog messages appear to
> > be spitting out to the tty we're on.  How would you go about redirecting
> > stderr on a shell your currently using, without killing/restarted.
> > 
> > Thanks for the help!
> > 
> > John
> > 
> > 
> > 
> > _______________________________________________
> > Ale mailing list
> > Ale at ale.org
> > http://www.ale.org/mailman/listinfo/ale
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://www.ale.org/mailman/listinfo/ale
-- 
James P. Kinney III          \Changing the mobile computing world/
CEO & Director of Engineering \          one Linux user         /
Local Net Solutions,LLC        \           at a time.          /
770-493-8244                    \.___________________________./
http://www.localnetsolutions.com

GPG ID: 829C6CA7 James P. Kinney III (M.S. Physics) <jkinney at localnetsolutions.com>
Fingerprint = 3C9E 6366 54FC A3FE BA4D 0659 6190 ADC3 829C 6CA7 

 This is a digitally signed message part