On Wed, Jul 03, 2024 at 11:01:41AM GMT, Stuart Henderson wrote:
> On 2024/07/02 20:57, Bjorn Ketelaars wrote:
> > The meta rc-script for Samba does not play nice with 'rcctl ls rogue'.
> > When a meta script is used, services started by the child scripts are
> > seen as rogue [0].
>
> There are 5
> On 3 Jul 2024, at 8:01 pm, Stuart Henderson wrote:
>
> On 2024/07/02 20:57, Bjorn Ketelaars wrote:
>> The meta rc-script for Samba does not play nice with 'rcctl ls rogue'.
>> When a meta script is used, services started by the child scripts are
>> seen as rogue [0].
>
> There are 5 others
On 2024/07/02 20:57, Bjorn Ketelaars wrote:
> The meta rc-script for Samba does not play nice with 'rcctl ls rogue'.
> When a meta script is used, services started by the child scripts are
> seen as rogue [0].
There are 5 others of these, and they do encapsulate knowledge of
which order the daemon
On Sat, Dec 09, 2023 at 01:03:31PM +, Edd Barrett wrote:
> (If we are fine with the general approach, and if this is something that we
> are
> going to need to do for other ports, perhaps it would be better for rc.d to
> have some kind of built-in support for using a daemon-wrapper? I don't kn
Hi,
I'm in the middle of this ongoing saga to get audio/navidrome to be startable
at boot time via an rc script. Despite the moaning below, I do like it as a
music player/streamer.
The problem: navidrome doesn't behave like a daemon:
- it doesn't setsid(2)
- it doesn't background itself
- it
On Fri, Jan 21, 2022 at 03:55:43PM +0100, Antoine Jacoutot wrote:
> On Fri, Jan 21, 2022 at 03:21:04PM +0100, Marc Espie wrote:
> > landry@ remarked that MODPY_BIN is probably
> > too specific when updating /etc/rc scripts from ports.
> >
> > (and it's also
On Fri, Jan 21, 2022 at 03:21:04PM +0100, Marc Espie wrote:
> landry@ remarked that MODPY_BIN is probably
> too specific when updating /etc/rc scripts from ports.
>
> (and it's also wrong, because pexp is a regexp)
>
> It should be trivial to add a
> MODPY_PEXP
> v
landry@ remarked that MODPY_BIN is probably
too specific when updating /etc/rc scripts from ports.
(and it's also wrong, because pexp is a regexp)
It should be trivial to add a
MODPY_PEXP
variable specifically for that, to facilitate restarts
after an upgrade
The question is: what shoul
Hi Landry,
Buildbot won't start from rc scripts anyway during system boot process
automatically.
I tried to run it by setting:
rcctl enable buildbot
...
stating network daemons: sshd bgpd relayd dhcpd smtpd vmd sndiod.
starting package daemons: buildbot(failed).
...
But it runs success
On 2020/08/28 11:55, Landry Breuil wrote:
> On Fri, Aug 28, 2020 at 09:46:31AM +, Martin wrote:
> > Hi Landry,
> >
> > Buildbot won't start from rc scripts anyway during system boot process
> > automatically.
> > I tried to run it by s
On Fri, Aug 28, 2020 at 09:46:31AM +, Martin wrote:
> Hi Landry,
>
> Buildbot won't start from rc scripts anyway during system boot process
> automatically.
> I tried to run it by setting:
>
> rcctl enable buildbot
>
> ...
> stating network daemons: sshd
I confirm buildbot-worker works since automat has been updated to
py-automat-0.8.0.
Great job, Landry!
Martin
‐‐‐ Original Message ‐‐‐
On Wednesday, July 22, 2020 7:18 PM, Landry Breuil wrote:
> On Wed, Jul 22, 2020 at 12:59:44PM +, Martin wrote:
>
> > It seems latest py-automat-2
On Wed, Jul 22, 2020 at 12:59:44PM +, Martin wrote:
> It seems latest py-automat-20.2.0 should be used with updated
> py-setuptools-49.x to run buildbot-worker correctly.
good catch, i think 0.8.0 is enough per
https://github.com/buildbot/buildbot/commit/a89eddb4acfdaa23bcb53806674a960e28cfcc
It seems latest py-automat-20.2.0 should be used with updated
py-setuptools-49.x to run buildbot-worker correctly.
Martin
‐‐‐ Original Message ‐‐‐
On Monday, July 20, 2020 8:45 PM, Martin wrote:
> Master has been created in /var/buildbot by:
>
> buildbot create-master master
> buildbot
Landry, thanks for reply.
Buildbot now starts from rc scripts successfully. It was /var/buildbot folder
contents permissions problem.
But now I'm stuck with buildbot-worker built from -current.
I've just created a worker by commands from README:
su -m _buildslave -c "buildbo
On Mon, Jul 20, 2020 at 08:45:53PM +, Martin wrote:
> Master has been created in /var/buildbot by:
>
> buildbot create-master master
> buildbot start master
> works.
>
> But I can't start Buildbot by
> rcctl start buildbot
>
> Any suggestions?
rcctl -d start buildbot, and look at /var/build
Master has been created in /var/buildbot by:
buildbot create-master master
buildbot start master
works.
But I can't start Buildbot by
rcctl start buildbot
Any suggestions?
Martin
On 11 okt 2014, at 14:42, Stuart Henderson wrote:
> OK? (Jakob, do you want to remain listed as maintainer of this?)
Nah, you can remove me.
jakob
Adds rc scripts for isc-dhcpd, isc-dhcrelay.
Adds a dedicated userid for the isc-dhcpd script.
Turn off groff, there are now only whitespace changes.
OK? (Jakob, do you want to remain listed as maintainer of this?)
Index: infrastructure/db/user.list
ml 26 Jul 2014 19:08:42 -
>@@ -65,6 +65,7 @@
> 2014/07/16 - lynx(1) moved to ports
>2014/07/22 - [ports] Increased file descriptor
>use in KDE4
>2014/07/23 - Changes to /etc infrastructure
>+2014/07/26 - rc scripts of both apache
>webservers renamed
>
>
&
anges to /etc infrastructure
+2014/07/26 - rc scripts of both apache webservers
renamed
@@ -694,6 +695,23 @@ additional log sockets in most cases, so
removed:
syslogd_flags="${syslogd_flags} -a /path/to/dev/log"
+
+
+
+2014/07/26 - [ports] rc scripts of both apache webse
2014/07/22 - [ports] Increased file descriptor use in
KDE4
2014/07/23 - Changes to /etc infrastructure
+2014/07/26 - rc scripts of both apache webservers
renamed
@@ -694,6 +695,23 @@ additional log sockets in most cases, so
removed:
syslogd_flags="${syslogd_flags} -a /
On 3/07/2014 8:29 PM, Craig R. Skinner wrote:
On 2014-07-03 Thu 16:23 PM |, Ian McWilliam wrote:
OK. Samba4 contains the /usr/local/bin/samba which is the full blown Active
Directory Server.
The RC script for that (when I write it) will need checks to make sure that
smbd / nmbd / winbindd are
On 2014-07-03 Thu 14:13 PM |, Ian McWilliam wrote:
>
> Secondly is it acceptable to create a common rc script to hold common subs
> used amongst multiple rc
> script for a port, eg samba.subr that will be used by smbd and nmbd rc
> scripts?
. /usr/local/libexec/samba-control ?
On 2014-07-03 Thu 16:23 PM |, Ian McWilliam wrote:
>
> OK. Samba4 contains the /usr/local/bin/samba which is the full blown Active
> Directory Server.
> The RC script for that (when I write it) will need checks to make sure that
> smbd / nmbd / winbindd are
> not running as those daemons are no
On 2014/07/03 16:23, Ian McWilliam wrote:
> OK, in that case, common functions will be duplicated 3 times in each
> of the smbd, nmbd, winbindd rc scripts.
rc scripts shouldn't be complicated/long enough that the duplication
is a problem :)
/rc.d/smbd check' ... instead.
> > > Secondly is it acceptable to create a common rc script to hold common
> > subs used amongst multiple rc
> > > script for a port, eg samba.subr that will be used by smbd and nmbd rc
> > scripts?
> >
> > No, the on
bes the scenarios that the samba4 stuff will give us.
> > Secondly is it acceptable to create a common rc script to hold common
> subs used amongst multiple rc
> > script for a port, eg samba.subr that will be used by smbd and nmbd rc
> scripts?
>
> No, the only time
nnot
start samba if it's already running?
If so, rc_check() does what you want. If you meant something else, please
elaborate :-)
> Secondly is it acceptable to create a common rc script to hold common subs
> used amongst multiple rc
> script for a port, eg samba.subr that will
[[ $? == 0 ]]; then
rc_err "$0: Cannot run while AD Server Running"
fi
}
Secondly is it acceptable to create a common rc script to hold common subs used
amongst multiple rc
script for a port, eg samba.subr that will be used by smbd and nmbd rc scripts?
Any thoughts / ideas a
Those need more love, but I've been unable to give it to them recently
so I'm sending to the list, maybe someone will manage to push it further
and update with changes that were made in the mean time to our tree.
My work is available in
https://github.com/jasperla/openbsd-wip/tree/master/net/ejabbe
On Fri, 14 Oct 2011, frantisek holop wrote:
> hmm, on Thu, Oct 13, 2011 at 11:49:32PM +0200, Antoine Jacoutot said that
> > On Thu, 13 Oct 2011, frantisek holop wrote:
> >
> > > also, some ports have executable pkg/*.rc file, some dont.
> > > what's the policy on that?
> >
> > What do you mean?
hmm, on Thu, Oct 13, 2011 at 11:49:32PM +0200, Antoine Jacoutot said that
> On Thu, 13 Oct 2011, frantisek holop wrote:
>
> > also, some ports have executable pkg/*.rc file, some dont.
> > what's the policy on that?
>
> What do you mean?
-rwxr-xr-x 1 root wheel 267 Apr 9 2011 /usr/ports/www
On Thu, 13 Oct 2011, frantisek holop wrote:
> also, some ports have executable pkg/*.rc file, some dont.
> what's the policy on that?
What do you mean?
> now on to my problem :]
> but whenever i make make update-plist after make fake, i get:
>
> ===> Updating plist for tinyproxy-1.8.3
> Sca
hi there,
i am confused about the rc scripts.
existing ports have pkg/daemon.rc files and a
@rcscript ${RCDIR}/daemon
line in PLIST
pkg_create(1) says:
@rcscript filename
Script for the /etc/rc.d framework. Contrary to @file, absolute
paths are okay, e.g
The following diff add a rc script and zap some stuff that now has
become useless.
thoroughly tested; have a look at it.
ciao,
David
Index: v5/Makefile
===
RCS file: /cvs/ports/www/tomcat/v5/Makefile,v
retrieving revision 1.17
diff
36 matches
Mail list logo
