PDA

View Full Version : 5.3.0b1 Shuts down



Manager Matt
2004-08-07, 00:05
I hate to break this up but I'm on Mandrake 9.2 not Windows. Where would
stderr normally end up on a linux box?
I'm sorry if it obvious, but I can't seem to remember. I can't find
anywhere in /var/log.

-Matt

-----Original Message-----
From: discuss-bounces (AT) lists (DOT) slimdevices.com
[mailto:discuss-bounces (AT) lists (DOT) slimdevices.com] On Behalf Of Roy M.
Silvernail
Sent: Friday, August 06, 2004 2:13 PM
To: Slim Devices Discussion
Subject: [slim] 5.3.0b1 Shuts down


Jeff Allison wrote:

>Supplement to this...the output goes to stderr rather than stdout.
>AFAIK, DOS does not let you redirect stderr, so if you want a logfile
>you need to use the command line switch --logfile logfile.txt. Using
>the normal redirect (>file) won't work.
>
>
It all depends on your command shell. According to
http://www.ss64.com/ntsyntax/redirection.html, the '2>' syntax works to
redirect stderr for NT (presumably cmd.exe). 4NT (shameless plug:
jpsoft.com) uses '>&' to redirect stderr. You should even be able to
redirect stdout to one file and stderr to another.

Piping (using the '|' character) is another kettle of pisces. Through at
least Win2K, command-line pipelines were still handled with hidden temporary
files (implying successive execution, not concurrent) and you were still
limited to two pipes in a single command. I don't know if that has been
improved in XP's command shell. Also don't know about the latest 4NT shell,
since my copy (though paid for) is several years old. If it ain't broke...
--
Roy M. Silvernail is roy (AT) rant-central (DOT) com, and you're not
"It's just this little chromium switch, here." - TFS
SpamAssassin->procmail->/dev/null->bliss
http://www.rant-central.com

kdf
2004-08-07, 00:14
by default, the init.d script set up a log in /tmp/slimserver.log. This is
easier than trying to mess with permissions. You can runa command line at any
point with:
/usr/local/slimserver/slimserver.pl --logfile ~/mylog.log


Quoting Manager Matt <managermatt (AT) earthlink (DOT) net>:

> I hate to break this up but I'm on Mandrake 9.2 not Windows. Where would
> stderr normally end up on a linux box?
> I'm sorry if it obvious, but I can't seem to remember. I can't find
> anywhere in /var/log.
>
> -Matt
>
> -----Original Message-----
> From: discuss-bounces (AT) lists (DOT) slimdevices.com
> [mailto:discuss-bounces (AT) lists (DOT) slimdevices.com] On Behalf Of Roy M.
> Silvernail
> Sent: Friday, August 06, 2004 2:13 PM
> To: Slim Devices Discussion
> Subject: [slim] 5.3.0b1 Shuts down
>
>
> Jeff Allison wrote:
>
> >Supplement to this...the output goes to stderr rather than stdout.
> >AFAIK, DOS does not let you redirect stderr, so if you want a logfile
> >you need to use the command line switch --logfile logfile.txt. Using
> >the normal redirect (>file) won't work.
> >
> >
> It all depends on your command shell. According to
> http://www.ss64.com/ntsyntax/redirection.html, the '2>' syntax works to
> redirect stderr for NT (presumably cmd.exe). 4NT (shameless plug:
> jpsoft.com) uses '>&' to redirect stderr. You should even be able to
> redirect stdout to one file and stderr to another.
>
> Piping (using the '|' character) is another kettle of pisces. Through at
> least Win2K, command-line pipelines were still handled with hidden temporary
> files (implying successive execution, not concurrent) and you were still
> limited to two pipes in a single command. I don't know if that has been
> improved in XP's command shell. Also don't know about the latest 4NT shell,
> since my copy (though paid for) is several years old. If it ain't broke...
> --
> Roy M. Silvernail is roy (AT) rant-central (DOT) com, and you're not
> "It's just this little chromium switch, here." - TFS
> SpamAssassin->procmail->/dev/null->bliss
> http://www.rant-central.com
>
>