what's wrong with output? can you post the output verbatim? I had a
look at the init script and it doesn't seem to print much.
> The start-stop daemon have the parameter --quiet
> I double check /etc/rc and the VERBOSE option for this kind of
> services is off
> i tried adding a /dev/null >& at the end of the start-stop daemon
> call, but didn't work.
not quite sure what "/dev/null >&" would do. I tried this with
net.eth0:
sudo /etc/init.d/net.eth0 restart >/dev/null
and it got rid of all the output. To be sure, you could add 2>&1
sudo /etc/init.d/net.eth0 restart >/dev/null 2>&1
> Any clues?
>
> Cheers!
HTH,
--
Iain Buchanan <iaindb at netspace dot net dot au>
Advertising Rule:
In writing a patent-medicine advertisement, first convince the
reader that he has the disease he is reading about; secondly,
that it is curable.
--
gento...@lists.gentoo.org mailing list
[snip]
> > > The start-stop daemon have the parameter --quiet
> > > I double check /etc/rc and the VERBOSE option for this kind of
> > > services is off
> > > i tried adding a /dev/null >& at the end of the start-stop daemon
> > > call, but didn't work.
> >
> >
> > not quite sure what "/dev/null >&" would do. I tried this with
> > net.eth0:
> > sudo /etc/init.d/net.eth0 restart >/dev/null
> >
> > and it got rid of all the output. To be sure, you could add 2>&1
> > sudo /etc/init.d/net.eth0 restart >/dev/null 2>&1
[snip]
> This is my tty1 after i start Networkmanager (not net.eth0, which are
> different services)
yes, I know :) I was just using net.eth0 as an example because I was
too lazy to install networkmanager and see for myself!
> and connect to a wireless network. The same happend when
> i bootup my system. I need my tty's to work and plus all thi info is odd and
> useless
[snip]
> Cheers, and thank for help us!
Did you try my suggestion?
> > sudo /etc/init.d/net.eth0 restart >/dev/null 2>&1
did it help? (substitute net.eth0 with NetworkManager ;)
It looks like all the output comes from this line in the init script
(again, only looking in the source, so YMMV)
start-stop-daemon --start --quiet --exec ${processname}
try adding
>/dev/null 2>&1
to the end of it.
HTH,
--
Iain Buchanan <iaindb at netspace dot net dot au>
Its name is Public Opinion. It is held in reverence. It settles everything.
Some think it is the voice of God.
-- Mark Twain
--
gento...@lists.gentoo.org mailing list
> try adding
> >/dev/null 2>&1
> to the end of it.
> Hi!
> about sudo /etc/init.d/net.eth0 restart >/dev/null 2>&1 I tried this
> before send this email, but the NetworkManager logs <info> and <debug>
> in the tty1 anyway, the only change is that i don't see any output in
> the terminal i run the command.
aaaaaaaaahhhhhhhhhhhh i see...
I thought you were on console 1, I didn't realise that NetworkManager
printed output to console 1 even if you started it from elsewhere... Now
I get it!
> about start-stop-daemon --start --quiet --exec ${processname} yes, i
> also tried your suggestion before send the email, but with the same
> bad result.
yes, won't work given what you've said...
> I not sure but for me, the parameter console=tty1 i have in the the
> kernel line i use in grub have something to do (i use fbsplash and
> fbcondecor), but is not the only reason, i check sabayon linux which
> use NetworkManager, fbsplash and fbconvecor just like the way i do,
> but NM don't do the same.
Sounds like NetworkManager is using syslog() to write to the log file,
and you have syslog set up to notify you. This usually happens by
printing messages to console 1! NetworkManager seems to translate glib
errors directly to syslog errors. Have a look at nm-logging.c if you
want to see more about that.
Anyway, depending on the logger you use (I use syslog-ng) you can set it
up not to be so verbose. syslog-ng allows you to filter based on
program name for example. man syslog-ng.conf for more info (or whatever
logger you use :)
Have a look at http://www.campin.net/syslog-ng.conf for some examples.
HTH,
--
Iain Buchanan <iaindb at netspace dot net dot au>
I can understand how they wouldn't let in those wild jungle apes, but what
about those really smart ones who live among us who rollerskate and smoke
cigars?
-- Homer Simpson, on Heaven
The Telltale Head
--
gento...@lists.gentoo.org mailing list
> > Sounds like NetworkManager is using syslog() to write to the log file,
> > and you have syslog set up to notify you. This usually happens by
> > printing messages to console 1! NetworkManager seems to translate glib
> > errors directly to syslog errors. Have a look at nm-logging.c if you
> > want to see more about that.
> >
> > Anyway, depending on the logger you use (I use syslog-ng) you can set it
> > up not to be so verbose. syslog-ng allows you to filter based on
> > program name for example. man syslog-ng.conf for more info (or whatever
> > logger you use :)
> >
> > Have a look at http://www.campin.net/syslog-ng.conf for some examples.
> >
> > HTH,
> >
> You rock! that was the key of my problem, i just added syslog-ng to the
> default run level and i don't get more that odd behavior of NetworkManager.
> Now is time to configure syslog-ng properly.
>
> Many thanks! :D
no probs. It took a while but we got there!
cya,
--
Iain Buchanan <iaindb at netspace dot net dot au>
* m2 stares at the monitor... it looks like a hamburger...
<Knghtbrd> m2 - that's a bad sign
--
gento...@lists.gentoo.org mailing list