On Wed, May 27, 2020 at 1:16 AM Antoine Jacoutot wrote:
>
> On Tue, May 26, 2020 at 05:16:44PM +0200, Why 42? The lists account. wrote:
> >
> > On Mon, May 25, 2020 at 04:51:51PM +0200, Antoine Jacoutot wrote:
> > > > ...
> > > > It looks as if the file has been sorted e.g.
> > > Did you use rcctl
On Tue, May 26, 2020 at 05:16:44PM +0200, Why 42? The lists account. wrote:
>
> On Mon, May 25, 2020 at 04:51:51PM +0200, Antoine Jacoutot wrote:
> > > ...
> > > It looks as if the file has been sorted e.g.
> > Did you use rcctl(8) ?
>
> Hi Antoine,
>
> You are correct, that does it. I checked t
On Mon, May 25, 2020 at 04:51:51PM +0200, Antoine Jacoutot wrote:
> > ...
> > It looks as if the file has been sorted e.g.
> Did you use rcctl(8) ?
Hi Antoine,
You are correct, that does it. I checked the history and after the
upgrade I had run rcctl to enable sensorsd. Just tested it again and
On Mon, May 25, 2020 at 03:22:11PM +0200, Why 42? The lists account. wrote:
>
> Hi All,
>
> After running sysupgrade to update from 6.6 (snapshot) to the newest
> version I noticed that the comments I added to /etc/rc.conf.local no
> longer made sense (if they ever did :)).
>
> It looks as if th
Lawrence Horvath wrote:
> when using rc.conf.local do you need to add
> #!/bin/sh -
> at the top of the file, or just start inserting lines?
The file is `sourced.' Which means it is read and executed by sh
running /etc/rc. You don't have to add a `shebang.' Also notice
the file isn't executable.
On Fri, Jan 19, 2007 at 03:18:09AM -0800, Lawrence Horvath wrote:
> when using rc.conf.local do you need to add
> #!/bin/sh -
> at the top of the file, or just start inserting lines?
The latter, it's included, not called separately (which would also make
getting at the variables somewhat difficult
Hey Lawrence,
> when using rc.conf.local do you need to add
> #!/bin/sh -
> at the top of the file, or just start inserting lines?
Its syntax is similar to rc.conf. Therefore: the latter.
HTH... Nico
Lawrence Horvath wrote:
when using rc.conf.local do you need to add
#!/bin/sh -
at the top of the file, or just start inserting lines?
thanks
Just start inserting the lines.
The hashbang is in the rc.conf script.
HTH
Fred
--
http://www.crowsons.net/puters/zaurus.php
On 4/20/06, Eduardo Alvarenga <[EMAIL PROTECTED]> wrote:
> > > The patch prevents rc from adding these two lines into the motd file.
> > > What I want is to not show information about the system and *JUST* my
> > > personal motd, for security purposes and to follow the company's
> > > policy.
> >
>
> > The patch prevents rc from adding these two lines into the motd file.
> > What I want is to not show information about the system and *JUST* my
> > personal motd, for security purposes and to follow the company's
> > policy.
>
> What security purposes? You have local users who you dont trust to
On Thu, Apr 20, 2006 at 10:30:10AM +0800, Lars Hansson wrote:
> On Thursday 20 April 2006 03:42, Eduardo Alvarenga wrote:
> > > Just leave the first two lines of motd intact, add you local motd after
> > > the two first lines, and your message will not be touched.
> >
> > The patch prevents rc from
On Thursday 20 April 2006 03:42, Eduardo Alvarenga wrote:
> > Just leave the first two lines of motd intact, add you local motd after
> > the two first lines, and your message will not be touched.
>
> The patch prevents rc from adding these two lines into the motd file.
> What I want is to not show
> Just leave the first two lines of motd intact, add you local motd after
> the two first lines, and your message will not be touched.
The patch prevents rc from adding these two lines into the motd file.
What I want is to not show information about the system and *JUST* my
personal motd, for secu
On Wed, Apr 19, 2006 at 03:50:45PM -0300, Eduardo Alvarenga wrote:
> Some companies ask sysadmins to put a specific message of the day for
> many purposes, this patch might become handy in such situations.
Did you read motd(5)?
On Friday 13 January 2006 07:15, Hannah Schroeter wrote:
> Hello!
>
> On Thu, Jan 12, 2006 at 09:36:14PM -0500, Dave Feustel wrote:
> >[...]
>
> >I also am using dhcp to get an ip address from verizon when I boot up.
>
> As long as you serve your own dhcp on different interfaces than the
> one y
Hello!
On Thu, Jan 12, 2006 at 09:36:14PM -0500, Dave Feustel wrote:
>[...]
>I also am using dhcp to get an ip address from verizon when I boot up.
As long as you serve your own dhcp on different interfaces than the
one you use dhclient on, it should be not much of a problem.
I've got a hairy s
On Thursday 12 January 2006 20:28, Alexander Hall wrote:
> Dave Feustel wrote:
> > I added the statement dchpd_flags="-d sis0 sis1 sis2 sis3" to rc.conf.local,
> > but dhcpd is not started at bootup. Is something else needed to get
> > dhcpd started automatically?
>
> Why would you want the output
chuckle
I never even saw the typo
On Thursday 12 January 2006 20:13, Jason Dixon wrote:
> On Jan 12, 2006, at 7:52 PM, Dave Feustel wrote:
>
> > I added the statement dchpd_flags="-d sis0 sis1 sis2 sis3" to
> > rc.conf.local,
> > but dhcpd is not started at bootup. Is something else needed to get
> > dhcpd started automatically?
Dave Feustel wrote:
I added the statement dchpd_flags="-d sis0 sis1 sis2 sis3" to rc.conf.local,
but dhcpd is not started at bootup. Is something else needed to get
dhcpd started automatically?
Why would you want the output to stderr when starting from /etc/rc? That
could be your problem.
On
On Thu, 12 Jan 2006, Dave Feustel wrote:
> I added the statement dchpd_flags="-d sis0 sis1 sis2 sis3" to rc.conf.local,
> but dhcpd is not started at bootup. Is something else needed to get
> dhcpd started automatically?
>
> Thanks,
> Dave Feustel
have you tried starting dhcpd with that command l
On Jan 12, 2006, at 7:52 PM, Dave Feustel wrote:
I added the statement dchpd_flags="-d sis0 sis1 sis2 sis3" to
rc.conf.local,
but dhcpd is not started at bootup. Is something else needed to get
dhcpd started automatically?
Spelling it right would help. :)
--
Jason Dixon
DixonGroup Consulti
On Thu, Jan 12, 2006 at 07:52:52PM -0500, Dave Feustel wrote:
> I added the statement dchpd_flags="-d sis0 sis1 sis2 sis3" to rc.conf.local,
> but dhcpd is not started at bootup. Is something else needed to get
> dhcpd started automatically?
>
> Thanks,
> Dave Feustel
> --
> Lose, v., experience
23 matches
Mail list logo