> From: Wojciech Puchar
>
> >> But still - do you know why it is necessary?
> >
> > An explanation written some 80 years ago;
> > 'Because that way it will work'.
> if you don't have anything to say - just don't do it.
practice what you preach.
___
fre
On Wed, 20 Jun 2012 08:02:48 -0400
Jerry wrote:
> On Wed, 20 Jun 2012 12:47:29 +0100
> RW articulated:
>
> > On Wed, 20 Jun 2012 09:45:07 +0100
> > Matthew Seaman wrote:
> >
> > > #!/bin/sh
> > > #
> > > # Persuade vboxheadless to start before samba.
> > >
> > > # PROVIDE: precedence
> > > # RE
cat precedence
#!/bin/sh
#
# Persuade postgresql to start before spamassassin.
# PROVIDE: precedence
# REQUIRE: postgresql
# BEFORE: spamd
% rcorder /etc/rc.d/* /usr/local/etc/rc.d/* | grep -E
'postgresql|precedence|sa-spamd'
/usr/local/etc/rc.d/postgresql
/usr/local/etc/rc.d/precedence
/us
On 6/20/12 11:09 AM, Matthew Seaman wrote:
> On 20/06/2012 09:51, Wojciech Puchar wrote:
>>>
>>> Create a new file in /usr/local/etc/rc.d/precedence with the following
>>> contents:
>>>
>>> #!/bin/sh
>>> #
>>> # Persuade
On Wed, 20 Jun 2012 12:47:29 +0100
RW articulated:
> On Wed, 20 Jun 2012 09:45:07 +0100
> Matthew Seaman wrote:
>
> > #!/bin/sh
> > #
> > # Persuade vboxheadless to start before samba.
> >
> > # PROVIDE: precedence
> > # REQUIRE: vboxheadless
> > # BEFORE: samba
> >
> > :
> >
> > Make it execu
But still - do you know why it is necessary?
An explanation written some 80 years ago;
'Because that way it will work'.
if you don't have anything to say - just don't do it.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mail
On Wed, 20 Jun 2012 09:45:07 +0100
Matthew Seaman wrote:
> #!/bin/sh
> #
> # Persuade vboxheadless to start before samba.
>
> # PROVIDE: precedence
> # REQUIRE: vboxheadless
> # BEFORE: samba
>
> :
>
> Make it executable. Note -- the ':' does seem to be necessary.
Why? None of the dummy scrip
> From owner-freebsd-questi...@freebsd.org Wed Jun 20 03:51:43 2012
> Date: Wed, 20 Jun 2012 10:51:04 +0200 (CEST)
> From: Wojciech Puchar
> To: Matthew Seaman
> Cc: freebsd-questions@freebsd.org
> Subject: Re: seems i cannot fully understand {/,/usr/local/}/etc/rc.d/*
>
#!/bin/sh
#
# Persuade vboxheadless to start before samba.
# PROVIDE: precedence
# REQUIRE: vboxheadless
# BEFORE: samba
:
Make it executable. Note -- the ':' does seem to be necessary.
thank you for help. I will test it when being on place and could reboot.
But still - do you know why it i
On Wed, 20 Jun 2012 10:51:04 +0200 (CEST)
Wojciech Puchar articulated:
> > Create a new file in /usr/local/etc/rc.d/precedence with the
> > following contents:
> >
> > #!/bin/sh
> > #
> > # Persuade vboxheadless to start before samba.
> >
> > #
On 20/06/2012 09:51, Wojciech Puchar wrote:
>>
>> Create a new file in /usr/local/etc/rc.d/precedence with the following
>> contents:
>>
>> #!/bin/sh
>> #
>> # Persuade vboxheadless to start before samba.
>>
>> # PROVIDE: precedence
>> #
Create a new file in /usr/local/etc/rc.d/precedence with the following
contents:
#!/bin/sh
#
# Persuade vboxheadless to start before samba.
# PROVIDE: precedence
# REQUIRE: vboxheadless
# BEFORE: samba
:
Make it executable. Note -- the ':' does seem to be necessary.
thank you f
On 20/06/2012 09:24, Wojciech Puchar wrote:
> i have samba server and few virtualbox sessions using vboxnet which is
> started by /usr/local/etc/rc.d/vboxheadless
>
> i want samba to be started AFTER vboxheadless as the latter configures
> vboxnet0 automatically when started, and s
i have samba server and few virtualbox sessions using vboxnet which is
started by /usr/local/etc/rc.d/vboxheadless
i want samba to be started AFTER vboxheadless as the latter configures
vboxnet0 automatically when started, and samba do bind to vboxnet0.
so i appended vboxheadless to REQUIRE
On Fri, Sep 17, 2010 at 01:02:03PM +0200, n dhert wrote:
> There seems to be a problem with starting up the IMAP proxy server
> imapproxyd:
> # /usr/local/etc/rc.d/imapproxyd start
> says
> Starting imapproxyd.
> but doesn't return the # prompt ...
> # ps -jawx | gre
There seems to be a problem with starting up the IMAP proxy server
imapproxyd:
# /usr/local/etc/rc.d/imapproxyd start
says
Starting imapproxyd.
but doesn't return the # prompt ...
# ps -jawx | grep imap
root 21490 21426 21490 64248 1 S+ 3 0:00.01 /bin/sh
/usr/local/etc/rc.d/imapproxyd start
On Mon, Jun 30, 2008 at 04:37:47PM -0400, fred wrote:
> Hi guys,
>
> Basically, I have 2 scripts in the folder /usr/local/etc/rc.d/
>
> Resin.sh and apache.sh
Are these the scripts provided by the ports? They should be installed
without the '.sh' extension. See rc(
Regarding the order of rc scripts,
On Mon, 30 Jun 2008, fred wrote:
I need resin to be started when apache is starting, how can I do that? I
can?t find any documentation on priority or order for startup scripts.
The rcorder(8) page will help you out. Note the PROVIDE and REQUIRE
keywords.
--On June 30, 2008 4:37:47 PM -0400 fred <[EMAIL PROTECTED]> wrote:
Hi guys,
Basically, I have 2 scripts in the folder “/usr/local/etc/rc.d/”
Resin.sh and apache.sh
I need resin to be started when apache is starting, how can I do that? I
can’t find any documentation on prior
At 03:37 PM 6/30/2008, fred wrote:
Hi guys,
Basically, I have 2 scripts in the folder "/usr/local/etc/rc.d/"
Resin.sh and apache.sh
I need resin to be started when apache is starting, how can I do that? I
can't find any documentation on priority or order for startup scr
Hi guys,
Basically, I have 2 scripts in the folder /usr/local/etc/rc.d/
Resin.sh and apache.sh
I need resin to be started when apache is starting, how can I do that? I
cant find any documentation on priority or order for startup scripts.
I have tried adding a line at the end of
onf so it is not needed.
I am wondering if this is causing something in rc confusion.
If that doesn't work. Turn off everything but 1 or 2 (at most) from
/usr/local/etc/rc.d scripts see if you can narrow it down.
Cheers,
Jeff
___
freebsd-question
On Sat, 19 Apr 2008 17:40:13 +0300
Manolis Kiagias <[EMAIL PROTECTED]> wrote:
> Ah!!! It just clicked! You got a lot of _enable="NO"
> This is rather unusual - you usually override something from
> /etc/defaults/rc.conf with a "YES"
>
> Your /etc/defaults/rc.conf has missing entries. It probably
Marco Beishuizen wrote:
On Sat, 19 Apr 2008 17:20:36 +0300
Manolis Kiagias <[EMAIL PROTECTED]> wrote:
securelevel -1 is fine. This is the default:
quote from init(8):
-1Permanently insecure mode - always run the system in level 0
mode. This is the default initial value.
Your problem
On Sat, 19 Apr 2008 17:20:36 +0300
Manolis Kiagias <[EMAIL PROTECTED]> wrote:
> securelevel -1 is fine. This is the default:
> quote from init(8):
>
> -1Permanently insecure mode - always run the system in level 0
> mode. This is the default initial value.
>
> Your problem lies elsewhere. I
Marco Beishuizen wrote:
On Sat, 19 Apr 2008 07:44:59 -0600
Eric <[EMAIL PROTECTED]> wrote:
are you changing the kernel security level in your rc.conf file? if
so, comment it out and reboot. that was an issue i had on a 6.x box
recently and commenting out the security level change fixed it
On Sat, 19 Apr 2008 07:44:59 -0600
Eric <[EMAIL PROTECTED]> wrote:
> are you changing the kernel security level in your rc.conf file? if
> so, comment it out and reboot. that was an issue i had on a 6.x box
> recently and commenting out the security level change fixed it
When I do a "sysctl -a |
On Sat, 19 Apr 2008 07:44:59 -0600
Eric <[EMAIL PROTECTED]> wrote:
> are you changing the kernel security level in your rc.conf file? if
> so, comment it out and reboot. that was an issue i had on a 6.x box
> recently and commenting out the security level change fixed it
No, I didn't change that.
searching it seems that none of the scripts
in /usr/local/etc/rc.d/ are being executed at startup. All scripts have
the extension .sh, have permission 755 and in rc.conf I have
local_startup="/usr/local/etc/rc.d".
I have no clue why they are not being executed.
are you changing the kernel
d
> - avahi
>
> They are all gnome related. I have in my rc.conf: oss_enable="YES",
> hald_enable="YES", avahi_daemon_enable="YES and dbus_enable="YES". The
> gnome FAQ mentiones to put gnome_enable="YES" in the rc.conf but that
> doesn&
Matthew Seaman wrote:
[EMAIL PROTECTED] wrote:
On Wed, 06 Feb 2008, Alex Zbyslaw wrote
Setuid/gid bits on shell scripts aren't considered safe, however and may
even be disabled.
THERE IS NO REASON FOR THIS, JUST USE THE FILE-SYSTEM TO PROTECT THE
FILES (MAKE THEM NOT WRITEABLE)
On Sunday 10 February 2008 11:13, Matthew Seaman wrote:
> [EMAIL PROTECTED] wrote:
> > On Wed, 06 Feb 2008, Alex Zbyslaw wrote
> > SNIP
> >
> >> Setuid/gid bits on shell scripts aren't considered safe, however and may
> >> even be disabled.
> >
> > THERE IS NO REASON FOR THIS,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
[EMAIL PROTECTED] wrote:
> On Wed, 06 Feb 2008, Alex Zbyslaw wrote
> SNIP
>> Setuid/gid bits on shell scripts aren't considered safe, however and may
>> even be disabled.
> THERE IS NO REASON FOR THIS, JUST USE THE FILE-SYSTEM
On Wed, 06 Feb 2008, Alex Zbyslaw wrote
SNIP
> Setuid/gid bits on shell scripts aren't considered safe, however and may
> even be disabled.
THERE IS NO REASON FOR THIS, JUST USE THE FILE-SYSTEM TO PROTECT THE FILES
(MAKE THEM NOT WRITEABLE). Scripts are no more susceptible t
to whoever without a password, and api can su to api
> without a password, and everyone else gets prompted.
It's actually built into /etc/rc.subr, the subversion server script is
a simple example of starting a daemon with a different user:
$ grep -v "^#" /usr/local/etc/rc
Zbigniew Szalbot wrote:
I have never really understood the thing about setuids, gid and etc. :)
I am not planning a restart so won't try it but I am pretty sure that
logs are created by root unless the api is started manually. No big
deal really but thanks for all the suggestions!
It's very s
to use cron for
automatic startups, which Lowell rightly pointed out to me. I just
loved the simplicity of symlinking sh scripts against
/usr/local/etc/rc.d/ :)
I personally much prefer scripts in rc.d because it's much easier to
migrate than crontabs, and if I never use a crontab I always
2008/2/6, Alex Zbyslaw <[EMAIL PROTECTED]>:
> Zbigniew Szalbot wrote:
>
> >I have looked at my /usr/local/etc/rc.d/ and realized that the symlink
> >I put there has the root as owner. It all works but I would rather use
> >a non-root user for to run that script.
>
Zbigniew Szalbot wrote:
I have looked at my /usr/local/etc/rc.d/ and realized that the symlink
I put there has the root as owner. It all works but I would rather use
a non-root user for to run that script.
$ ls -l /usr/local/etc/rc.d/
lrwxr-xr-x 1 root wheel40 May 9 2007 sender.sh
Hello Alex,
2008/2/6, Alex Zbyslaw <[EMAIL PROTECTED]>:
> Zbigniew Szalbot wrote:
>
> >Hello,
> >
> >I have looked at my /usr/local/etc/rc.d/ and realized that the symlink
> >I put there has the root as owner. It all works but I would rather use
>
Zbigniew Szalbot wrote:
Hello,
I have looked at my /usr/local/etc/rc.d/ and realized that the symlink
I put there has the root as owner. It all works but I would rather use
a non-root user for to run that script.
$ ls -l /usr/local/etc/rc.d/
lrwxr-xr-x 1 root wheel40 May 9 2007
"Zbigniew Szalbot" <[EMAIL PROTECTED]> writes:
> I have looked at my /usr/local/etc/rc.d/ and realized that the symlink
> I put there has the root as owner. It all works but I would rather use
> a non-root user for to run that script.
>
> $ ls -l /usr/local/etc/rc
Hello,
I have looked at my /usr/local/etc/rc.d/ and realized that the symlink
I put there has the root as owner. It all works but I would rather use
a non-root user for to run that script.
$ ls -l /usr/local/etc/rc.d/
lrwxr-xr-x 1 root wheel40 May 9 2007 sender.sh ->
/usr/home/api/sen
Samba tdb files:
.
.
.
.
.
.
.
done
Starting Init
Starting Samba
Removing stale Samba tdb files:
.
.
.
.
.
.
.
done
-
i have only 2 scripts in /usr/local/etc/rc.d:
init.sh, which starts vsftpd and a dyndns client
and samba.sh.
As you can see
at I should look for?
> >
> > Thanks,
> >
> > P.S. - I wish you all a happy 2008 ! My guts keep telling me that this is
> > going to be a great year for FreeBSD !!
>
> Check your /etc/rc.conf settings, e.g. local_startup or whatever
> controls rc.d directories. Either
stale Samba tdb files:
.
.
.
.
.
.
.
done
-
i have only 2 scripts in /usr/local/etc/rc.d:
init.sh, which starts vsftpd and a dyndns client
and samba.sh.
As you can see, the scripts in that directory are beeing ran twice !. I looked
up and down the server
:
.
.
.
.
.
.
.
done
-
i have only 2 scripts in /usr/local/etc/rc.d:
init.sh, which starts vsftpd and a dyndns client
and samba.sh.
As you can see, the scripts in that directory are beeing ran twice !. I looked
up and down the server (/etc/init.d
On Wed, 7 Mar 2007 13:40:09 -0600
Dan Nelson <[EMAIL PROTECTED]> wrote:
> In the last episode (Mar 07), Don O'Neil said:
> > Are there any special naming requirements for scripts in
> > /usr/local/etc/rc.d for 6.1?
> >
> > Someone is telling me the
On Wed, Mar 07, 2007 at 10:58:22AM -0800, Don O'Neil wrote:
> Are there any special naming requirements for scripts in /usr/local/etc/rc.d
> for 6.1?
>
> Someone is telling me they need to have a .sh suffix to startup correctly,
> but in past versions of FreeBSD anything yo
In the last episode (Mar 07), Don O'Neil said:
> Are there any special naming requirements for scripts in
> /usr/local/etc/rc.d for 6.1?
>
> Someone is telling me they need to have a .sh suffix to startup
> correctly, but in past versions of FreeBSD anything you put in there
Someone is telling me they need to have a .sh suffix to startup correctly,
but in past versions of FreeBSD anything you put in there would run as long
as it was executable.
It need not have an sh extension. The MySQL port, for example,
installs /usr/local/etc/rc.d/mysql-server, which works fine
Are there any special naming requirements for scripts in /usr/local/etc/rc.d
for 6.1?
Someone is telling me they need to have a .sh suffix to startup correctly,
but in past versions of FreeBSD anything you put in there would run as long
as it was executable.
Just trying to confirm the correct
Hi, Brooks!
Thanks for the advice, it helped!
> I have to say that I use this loader.rc for network boot:
> load /boot/kernel/kernel
> echo \007\007
> set console="vidconsole"
> autoboot
Do you by chance have a /boot.config? It sounds like your system is
probably running on a serial console.
On Thu, Feb 01, 2007 at 11:23:23AM +0900, Artem Kazakov wrote:
> Hello everyone,
>
> I'm using 6-stable on 4 amd64 machines. One of them has FreeBSD on its
> local hard drive and others are booted via network with PXE.
> But I encounter that /usr/local/etc/rc.d/* are not
Hello everyone,
I'm using 6-stable on 4 amd64 machines. One of them has FreeBSD on its
local hard drive and others are booted via network with PXE.
But I encounter that /usr/local/etc/rc.d/* are not executed during the
boot process?
Is there some kind of option to change this?
Or may
On Tue, 16 Jan 2007 21:51:08 +0500, Dan Nelson <[EMAIL PROTECTED]>
wrote:
Try shutting squid down manually from a shell prompt, then switch to
another window/vty and take a look at /usr/local/squid/logs/cache.log .
My guess is it's waiting for an active client connection to exit. The
default
[EMAIL PROTECTED] wrote:
> It seems something strange with squid-2.6.6 on my FreeBSD 6.2-PRERELEASE
> box.
> After running 'usr/local/etc/rc.d/squid stop' (and therefore during
> system shutdown on 'Ctrl+Alt+Delete' or ACPI power button pushing) I see
>
In the last episode (Jan 16), [EMAIL PROTECTED] said:
> It seems something strange with squid-2.6.6 on my FreeBSD
> 6.2-PRERELEASE box. After running 'usr/local/etc/rc.d/squid stop'
> (and therefore during system shutdown on 'Ctrl+Alt+Delete' or ACPI
> power but
It seems something strange with squid-2.6.6 on my FreeBSD 6.2-PRERELEASE
box.
After running 'usr/local/etc/rc.d/squid stop' (and therefore during system
shutdown on 'Ctrl+Alt+Delete' or ACPI power button pushing) I see the
following:
Stopping squid.
Waiting for PIDS: 5
On 12/23/06, Kevin Brunelle <[EMAIL PROTECTED]> wrote:
I was unintentionally confusing in my answer. Sorry about that. If your
startup script is in the old style, it will be handled by /etc/rc.d/localpkg
when that is called during the boot process. That is ONLY if it's the old
style.
I shoul
> So rcorder is not used for the rc scripts in /usr/local/etc/rc.d? That
> explains much, since I have a runsvstat.sh script needed to start
> runit, and a script to start one of its services starts with an 'm'
> and is executing first, which I don't want.
>
>
On 12/23/06, Kevin Brunelle <[EMAIL PROTECTED]> wrote:
They are called from /etc/rc.d/localpkg if they are the old style.
The directories searched are defined with local_startup (which defaults
to: /usr/local/etc/rc.d /usr/X11R6/etc/rc.d).
Ok, looking in localpkg, I see this.
pkg
ail"
> files=`rcorder ${skip} /etc/rc.d/* 2>/dev/null`
>
> for _rc_elem in ${files}; do
> run_rc_script ${_rc_elem} ${_boot}
> done
>
> So rcorder is run over /etc/rc.d/*.
>
> When is the same done for /usr/local/etc/rc.d/*?
>
> Thanks,
> Mike
They
rcorder ${skip} /etc/rc.d/* 2>/dev/null`
for _rc_elem in ${files}; do
run_rc_script ${_rc_elem} ${_boot}
done
So rcorder is run over /etc/rc.d/*.
When is the same done for /usr/local/etc/rc.d/*?
1. grep for rcorder in rc
2. grep for local_rc in rc.subr
___
; do
run_rc_script ${_rc_elem} ${_boot}
done
So rcorder is run over /etc/rc.d/*.
When is the same done for /usr/local/etc/rc.d/*?
Thanks,
Mike
--
Michael P. Soulier <[EMAIL PROTECTED]>
"Any intelligent fool can make things bigger and more complex... It takes a
touch of genius
Hi,
I'm hoping to get into the spirit of the new rc.d script specs (REQUIRES,
PROVIDES, command=, etc) on a new server I'm building. The old script I
was using looked like this:
/usr/local/etc/rc.d/start-all-foo.sh
[ -x /usr/local/bin/foo ] && su foo-role -c "/usr/local
Andrey V. Semyonov wrote:
The most terrible thing is than you can't extract a value from a
variable, which you name by some dynamic sting (you can't extract a
variable by name set in other variable partly or the whole)
Sorry, I'm too hurry.
if ! /bin/test -z $(eval echo \$${name}${common_var
Mike Hunter wrote:
Hi,
I'm hoping to get into the spirit of the new rc.d script specs (REQUIRES,
PROVIDES, command=, etc) on a new server I'm building. The old script I
was using looked like this:
I have several questions about how to replicate this behavior. I'm still
deciding whether I'm wi
Hi,
I'm hoping to get into the spirit of the new rc.d script specs (REQUIRES,
PROVIDES, command=, etc) on a new server I'm building. The old script I
was using looked like this:
/usr/local/etc/rc.d/start-all-foo.sh
[ -x /usr/local/bin/foo ] && su foo-role -c "/usr/local
Philip Hallstrom writes:
Put the following into the jail's /etc/rc.conf:
early_late_divider="NETWORKING"
Thanks!
That worked.
That worked for me. My memory is this isn't a *real* solution, but that
it does the trick (going off some posts I found on the issue when this
happened to me)
It
I have a jail, running in FreeBSD 6, which starts sshd and syslogd, but
doesn't start any of the programs from /usr/local/etc/rc.d
All the appropriate variables are in /etc/rc.conf for the various programs
(postfix, spamd, clamsmtp, freshclam). I am able to run the programs manuall
I have a jail, running in FreeBSD 6, which starts sshd and syslogd, but
doesn't start any of the programs from /usr/local/etc/rc.d
All the appropriate variables are in /etc/rc.conf for the various programs
(postfix, spamd, clamsmtp, freshclam). I am able to run the programs
manually by
I have one script in /usr/local/etc/rc.d that doesn't run. Any ideas why?
It is marked as executable
ls -l /usr/local/etc/rc.d/
-r-xr-xr-x 1 root wheel 441B Dec 30 20:36 start-program.sh
The script is just:
#!/bin/sh
log="/var/log/program.log"
echo -&
On Sun, Oct 16, 2005 at 11:16:12AM +0930, Daniel O'Connor wrote:
> On Sun, 16 Oct 2005 04:42, Lefteris Tsintjelis wrote:
> > I am getting all these "no provider" and rcorder doesn't seem to
> > work properly under /usr/local/etc/rc.d. Services seem to start
>
On Sun, 16 Oct 2005 04:42, Lefteris Tsintjelis wrote:
> I am getting all these "no provider" and rcorder doesn't seem to
> work properly under /usr/local/etc/rc.d. Services seem to start
> alphabetically and not in the right order specified. The keywords
> REQUIRE, PROVI
On 2005-10-16 00:41, Lefteris Tsintjelis <[EMAIL PROTECTED]> wrote:
> Giorgos Keramidas wrote:
> >% flame:/home/keramida$ rcorder /etc/rc.d/* /usr/local/etc/rc.d/* >/dev/null
> >% rcorder: Circular dependency on provision `mountcritremote' in file
> >`/etc/rc.d
Giorgos Keramidas wrote:
[...]
These look like stuff that is "provided" by /etc/rc.d/* scripts.
Try including all the scripts in the rcorder command line:
% flame:/home/keramida$ rcorder /usr/local/etc/rc.d/* >/dev/null
% rcorder: file `/usr/local/etc/rc.d/samba.sh'
On 2005-10-15 22:12, Lefteris Tsintjelis <[EMAIL PROTECTED]> wrote:
> I am getting all these "no provider" and rcorder doesn't seem to work
> properly under /usr/local/etc/rc.d. Services seem to start
> alphabetically and not in the right order specified. The keywo
On 2005-10-15 22:12, Lefteris Tsintjelis <[EMAIL PROTECTED]> wrote:
> I am getting all these "no provider" and rcorder doesn't seem to work
> properly under /usr/local/etc/rc.d. Services seem to start
> alphabetically and not in the right order specified. The keywo
I am getting all these "no provider" and rcorder doesn't seem to
work properly under /usr/local/etc/rc.d. Services seem to start
alphabetically and not in the right order specified. The keywords
REQUIRE, PROVIDE, BEFORE and KEYWORD seem to be ignored. Services
like SERVERS, NETWORK
"Chad Leigh -- Shire.Net LLC" <[EMAIL PROTECTED]> writes:
> I read the handbook and the man page for rc and one question remains.
>
> For scripts in /usr/local/etc/rc.d it appears that the assumption is
> that all scripts are old style and so, no matter if they are
I read the handbook and the man page for rc and one question remains.
For scripts in /usr/local/etc/rc.d it appears that the assumption is
that all scripts are old style and so, no matter if they are rcGN
style scripts or not, they will all run in lexographic order, right?
Thanks
Chad
On Thursday 10 March 2005 06:45 am, Fafa Diliha Romanova wrote:
> hello.
>
> i'm just wondering how to deal with the way the rc.d scripts
> echo on startup. like, some of the rc.d scripts contain the
> echo " daemon", while some echo "daemon", so on startup whereas
> it should look like:
>
> daemon
;,
> so on startup whereas it should look like:
>
> daemon daemon deamon
>
> it may look like:
>
> daemondaemon daemon 1.2 Loaded successfully!daemon
>
> is there a uniform way to identify echos and make them display properly?
> thanks!
I usually edit the offending sc
hello.
i'm just wondering how to deal with the way the rc.d scripts echo on startup.
like, some of the rc.d scripts contain the echo " daemon", while some echo
"daemon",
so on startup whereas it should look like:
daemon daemon deamon
it may look like:
daemondaemon daemon 1.2 Loaded successfull
> >> On my 4.10 box, there is a mysql-server script in
> /usr/local/etc/rc.d
> >> and nothing
> >> in /etc/rc.conf, yet mysql-server starts up a
> boot time.
> >> Why?
(the following is true for 4.x)
Check the /etc/defaults/rc.conf file
You&#x
Toomas Aas wrote:
Andy Firman wrote:
On my 4.10 box, there is a mysql-server script in /usr/local/etc/rc.d
and nothing
in /etc/rc.conf, yet mysql-server starts up a boot time.
Why?
Your mysql-server port was probably installed before 31.10.2004. It was
modified to use rc.conf variables at
Andy Firman wrote:
On my 4.10 box, there is a mysql-server script in /usr/local/etc/rc.d and nothing
in /etc/rc.conf, yet mysql-server starts up a boot time.
Why?
Your mysql-server port was probably installed before 31.10.2004. It was
modified to use rc.conf variables at that date (see /usr
reeBSD box and there is a
> > >proftpd.sh script in the /usr/local/etc/rc.d directory.
> > >
> > >There is also this entry in /etc/rc.conf:
> > >proftpd_enable="YES"
> > >
> > >There is no need for entries in /etc/rc.conf
> > &g
* Paul Schmehl <[EMAIL PROTECTED]> [1210 17:10]:
> --On Thursday, December 02, 2004 07:39:00 AM -0900 Andy Firman
> <[EMAIL PROTECTED]> wrote:
>
> >
> >I just took over a FreeBSD box and there is a
> >proftpd.sh script in the /usr/local/etc/rc.d directory.
--On Thursday, December 02, 2004 07:39:00 AM -0900 Andy Firman
<[EMAIL PROTECTED]> wrote:
I just took over a FreeBSD box and there is a
proftpd.sh script in the /usr/local/etc/rc.d directory.
There is also this entry in /etc/rc.conf:
proftpd_enable="YES"
There is no need for
Andy
err no.
the entry in /usr/local/etc/rc.d will read the rc.conf to get variables.
Normally done thisway when program is installed from ports rather than
hand compiled...
--
Martin Hepworth
Snr Systems Administrator
Solid State Logic
Tel: +44 (0)1865 842300
Andy Firman wrote:
I just took
I just took over a FreeBSD box and there is a
proftpd.sh script in the /usr/local/etc/rc.d directory.
There is also this entry in /etc/rc.conf:
proftpd_enable="YES"
There is no need for entries in /etc/rc.conf
if the script exists in /usr/local/etc/rc.d ri
--- Matthew Seaman <[EMAIL PROTECTED]>
wrote:
> Since your script can start up Swatch when run by
> hand, but not during
> system boot, I suspect the problem is either to do
> with having or not
> having a tty at startup time, or else to do with
> boot order -- maybe
> if you try changing the scri
On Thu, Oct 14, 2004 at 09:47:03PM -0700, Henri Prudhomme wrote:
> By RTFM my understanding is that for 4.10 nothing
> special is needed. Just make sure the script is in the
> rc.d directory, is executable (755) and ends with .sh.
> The script is owned by root and wheel.
It depends. More and mor
I am running freebsd 4.10. I have a case start / stop
script for Swatch in /usr/local/etc/rc.d. I can run
the script manually as superuser and it works
correctly - Swatch correctly starts and stops, and
runs as a daemon in the backgound. But when I reboot
the server, the Swatch service doesn&#
ere is rcorder being kicked off on
> /usr/local/etc/rc.d to use rcNG...
>
> I see that /etc/rc.d/localpkg is still skimming for *.sh and running
> them, and not doing the rcorder method.
Correct. The rcorder method is used only for /etc/rc.d scripts. See:
$ grep -n rcorder /etc/rc
Learn something new every day, just learning the internals of
FreeBSD-5.2.1 (have been sticking to the 4.x-STABLEs) and rolling out my
first 5.x system.
rcNG is really nice, but where is rcorder being kicked off on
/usr/local/etc/rc.d to use rcNG...
I see that /etc/rc.d/localpkg is still
> I'm not sure we are talking about the same thing. Is the "x"
> executable bit set when you do an ls -l in /usr/local/etc/rc.d?
>
> # ls -l /usr/local/etc/rc.d
> -r-xr-xr-x 1 root wheel635 Jun 15 05:58 apache.sh
>^ ^ ^
>
> Are these bits set
, but if I add
them (I mean
'them' == the full path to their starting scripts in /usr/local/etc/rc.d/)
to the end of
apache`s script, then they are starting..
Are they all set to executable (chmod +x)?
Yes, they all are executable - if I add them to the end of the only script
that i
1 - 100 of 138 matches
Mail list logo
