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(8).
> I need resin to be start
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 priority or order
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 scripts.
I have tr
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 r
RW <[EMAIL PROTECTED]> writes:
> On Mon, 11 Feb 2008 21:55:28 +
> RW <[EMAIL PROTECTED]> wrote:
>
>> On Mon, 11 Feb 2008 14:19:21 -0500
>> Lowell Gilbert <[EMAIL PROTECTED]> wrote:
>>
>> > RW <[EMAIL PROTECTED]> writes:
>>
>> > > I could imagine screwing-up the operation of rc.shutdown with
On Mon, 11 Feb 2008 21:55:28 +
RW <[EMAIL PROTECTED]> wrote:
> On Mon, 11 Feb 2008 14:19:21 -0500
> Lowell Gilbert <[EMAIL PROTECTED]> wrote:
>
> > RW <[EMAIL PROTECTED]> writes:
>
> > > I could imagine screwing-up the operation of rc.shutdown with a
> > > syntax error, but I don't see how I
On Mon, 11 Feb 2008 14:19:21 -0500
Lowell Gilbert <[EMAIL PROTECTED]> wrote:
> RW <[EMAIL PROTECTED]> writes:
> > I could imagine screwing-up the operation of rc.shutdown with a
> > syntax error, but I don't see how I could stop it being run at all.
> > As I understand it rc.shutdown is run from
On Mon, Feb 11, 2008 at 06:06:47PM +, RW wrote:
> On Sun, 10 Feb 2008 04:02:15 +
> RW <[EMAIL PROTECTED]> wrote:
>
> >
> > Afer putting in some extra logging to check something, I've just
> > noticed that my rc.d scripts are not being run
RW <[EMAIL PROTECTED]> writes:
> On Sun, 10 Feb 2008 04:02:15 +
> RW <[EMAIL PROTECTED]> wrote:
>
>>
>> Afer putting in some extra logging to check something, I've just
>> noticed that my rc.d scripts are not being run at shutdown.
>>
&g
On Sun, 10 Feb 2008 04:02:15 +
RW <[EMAIL PROTECTED]> wrote:
>
> Afer putting in some extra logging to check something, I've just
> noticed that my rc.d scripts are not being run at shutdown.
>
> By way of confirmation, my entropy file, which is written out by
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
Afer putting in some extra logging to check something, I've just noticed
that my rc.d scripts are not being run at shutdown.
By way of confirmation, my entropy file, which is written out by an
rc.d script, has not been written to for a week (I shut-down most
nights). I don't re
On Wed, 06 Feb 2008 17:09:50 +
Alex Zbyslaw <[EMAIL PROTECTED]> wrote:
> 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 know
> where to look.
>
> It looks to me like you shouldn't be starting the demon as us
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
Zbigniew Szalbot wrote:
Thank you. I realized this was the case before I wrote previous
message. The thing is the real file is owned by user api. However,
when the application is started following a reboot, its logs are
created by user root, whereas when I start it by hand as user api, its
logs
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.
> >
> >$ ls -l /usr/local/etc/rc.d/
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 ->
/u
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
> >a non-root user for to run that script.
> >
> >$
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 sender.
"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.d/
> lrwxr-xr-x 1 root wheel
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/sender/
oops, sent a reply to the wrong list a bit ago... Anyway, it is still
not working.
I forgot to mentions, sorry, doing
$ /usr/local/etc/rc.d/sb_server start
works just fine.
I used "/usr/bin/env python" because I would like to add this to the
port that installs the server this script starts, an
On Sun, 25 Mar 2007 23:03:38 -0400
Kevin Brunelle <[EMAIL PROTECTED]> wrote:
> > >Does anyone know how to make a script in /etc/rc.d run last? For
> > >instance I want dhclient to be the last script in /etc/rc.d/ to
> > >run. Any help is much appreciated.
> >
> > This may have already been answe
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:owner-freebsd-
> [EMAIL PROTECTED] On Behalf Of Jack Stone
> Sent: Sunday, March 25, 2007 8:09 AM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: RE: rc.d scripts
>
> >From: Tom Grove <[EMAIL PROTE
> >Does anyone know how to make a script in /etc/rc.d run last? For instance
> >I want dhclient to be the last script in /etc/rc.d/ to run. Any help is
> >much appreciated.
>
> This may have already been answered by others, but I believe just rename
> the script with a prefix of "z" for example:
From: Tom Grove <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: rc.d scripts
Date: Fri, 23 Mar 2007 09:15:29 -0400
Does anyone know how to make a script in /etc/rc.d run last? For instance
I want dhclient to be the last script in /etc/rc.d/ to run. Any help is
much appreciated.
On Fri, 23 Mar 2007 09:15:29 -0400
Tom Grove <[EMAIL PROTECTED]> wrote:
> Does anyone know how to make a script in /etc/rc.d run last? For
> instance I want dhclient to be the last script in /etc/rc.d/ to run.
> Any help is much appreciated.
Just have it require the last script, which is bgfs
Does anyone know how to make a script in /etc/rc.d run last? For
instance I want dhclient to be the last script in /etc/rc.d/ to run.
Any help is much appreciated.
-Tom
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/
This:
(0) ~ > sudo rcorder /usr/local/etc/rc.d/* /etc/rc.d/*
/etc/rc.d/dumpon
/etc/rc.d/initrandom
/etc/rc.d/geli
/etc/rc.d/gbde
/etc/rc.d/encswap
/etc/rc.d/ccd
/etc/rc.d/swap1
/etc/rc.d/mdconfig
/etc/rc.d/ramdisk
/etc/rc.d/early.sh
/etc/rc.d/fsck
/etc/rc.d/root
/etc/rc.d/mountcritlocal
/etc/rc.
what does: $ sudo rcorder /usr/local/etc/rc.d/* /etc/rc.d/*
..look like?
~BAS
On Wed, 2007-03-21 at 10:57 -0700, Chuck Swiger wrote:
> On Mar 21, 2007, at 10:52 AM, Jim Stapleton wrote:
> > I created a script in my /usr/local/etc/rc.d directory, but for some
> > reason it doesn't auto start whe
On Mar 21, 2007, at 10:52 AM, Jim Stapleton wrote:
I created a script in my /usr/local/etc/rc.d directory, but for some
reason it doesn't auto start when I start my machine. I added entries
to the rc.conf that I thought should work, but they did not. On a
related not, my rc.conf file doesn't seem
I created a script in my /usr/local/etc/rc.d directory, but for some
reason it doesn't auto start when I start my machine. I added entries
to the rc.conf that I thought should work, but they did not. On a
related not, my rc.conf file doesn't seem to disable autostart of
sendmail. Could anyone advi
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 executed during the
> boot
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 be I misconf
Since src u/g 5.4->6 the *_enable variables in rc.conf for local rc.d
scripts are being ignored. For example, neither lisad (for KDE LAN
Browsing) or giftd (for giFT) are starting.
In rc.conf I have:
lisa_enable="YES" # Lisa daemon for LAN Browsing in Konqueror
gift
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 2005-03-10 06:45, Fafa Diliha Romanova <[EMAIL PROTECTED]> 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"
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:
daemo
Hi,
I have a freshly installed FreeBSD 5.3, I keep getting an error "path:
not found" when rc-scripts are run, this holds both for the base scripts
in /etc/rc.d and installed scripts in /usr/local/etc/rc.d - also, the
cron job which runs save-entropy every 11 minutes sends this error.
But I don
On May 12, 2004, at 5:06 PM, Tim Aslat wrote:
In the immortal words of "Chad Leigh -- Shire.Net LLC"
<[EMAIL PROTECTED]>...
"The best way to handle rc.local, however, is to separate it
out into rc.d/ style scripts and place them under
/usr/local/etc/rc.d/."
That's right
So I created an rc.d
In the immortal words of "Chad Leigh -- Shire.Net LLC"
<[EMAIL PROTECTED]>...
> "The best way to handle rc.local, however, is to separate it
> out into rc.d/ style scripts and place them under
> /usr/local/etc/rc.d/."
That's right
> So I created an rc.d style script for my own service and
Hi
In the man pages for rc it says:
"The best way to handle rc.local, however, is to separate it
out into rc.d/ style scripts and place them under
/usr/local/etc/rc.d/."
So I created an rc.d style script for my own service and stuck it in
/usr/local/etc/rc.d/. It does not have a .sh on t
47 matches
Mail list logo
