Starting with FreeBSD [rc.conf, ps(1) options, kernel modules, and other stuff] (was: Re: Procedures)

Ronny Machado C. ronny.machado at cajalosandes.cl
Fri Oct 21 06:21:36 PDT 2005


thanks a lot Giorgos...you were very kind...

ronny

-----Mensaje original-----
De: Giorgos Keramidas [mailto:keramida at ceid.upatras.gr]
Enviado el: Viernes, 21 de Octubre de 2005 8:00
Para: Ronny Machado C.
CC: freebsd-questions at freebsd.org
Asunto: Starting with FreeBSD [rc.conf, ps(1) options, kernel modules,
and other stuff] (was: Re: Procedures)


On 2005-10-21 08:30, "Ronny Machado C." <ronny.machado at cajalosandes.cl> wrote:
> Hi list....
> I'm new to freebsd, I come from Linux world, and I dont?t fully
> understand some procedures:

> * How can I get some daemons working at boot time? In Linux you can do
> it via rc.* directories and S* scripts, but in freeBSD I don't know
> how, I've put scripts in rc.d but they don't execute at boot time, Is
> there a way to do it via rc.conf?

By setting options in the ``/etc/rc.conf'' file.  The full list of
available options is listed with a fair bit of comments in
``/etc/defaults/rc.conf'' and is documented extensively in the
rc.conf(5) manpage.

> * When I do a "ps -fe | grep some-process" I don't get any answer, so
> I can't realise if a process is running, I've got to do a top to get
> to it

The -ef options are not doing what you think.  They work on Linux,
Solaris and other UNIXes that follow the System-V 'style', but not
in BSD.  Try -aux instead:

	# ps -aux | grep some-process

or even better, if you're just looking for a short list of PIDs and
names, use pgrep(1):

	# pgrep -l some-process

> * My sound card is a Sound Blaster Live!, I've tried to load it by
> means of kldload emu10k1, it worked but I can't get it to
> work. Honestly I haven't configured MYKERNEL since I still don't
> understand the process.

Not sure about that.  I never worked with an SB Live!.

> * How can I list the modules in the kernel?

With kldstat(8).

> * I'd like to know if the following messages are due to some failure
> or they are normal, and if the noip problem is produced by the ppp
> warnings

> Oct 18 12:22:13 nostromo noip2[707]: Can't gethostbyname for dynupdate.no-ip.com
> Oct 18 12:22:13 nostromo noip2[707]: Can't get our visible IP address from dynupdate.no-ip.com

This is a DNS resolution problem.  We'd have to know a bit more about
your network connection to the world, and your existing DNS setup to
answer if this is normal.

> Oct 18 12:23:01 nostromo ppp[217]: tun0: Warning: deflink: Reducing configured MRU from 1500 to 1492
> Oct 18 12:25:06 nostromo ppp[217]: tun0: Warning: deflink: Reducing configured MRU from 1500 to 1492
> Oct 18 12:27:11 nostromo ppp[217]: tun0: Warning: deflink: Reducing configured MRU from 1500 to 1492

That's mostly harmless.



More information about the freebsd-questions mailing list