On Sun, Mar 17, 2019 at 09:25:32PM +0800, Casper Ti. Vector wrote:
> Since the first announcement [1] of slew [2], a few people expressed
> interest in the project, but I have received little feedback regarding
> its technical contents. Therefore although I have successfully deployed
> slew on a f
On Wed, Mar 20, 2019 at 01:14:39PM +0800, Casper Ti. Vector wrote:
> pkill(1), killall(1) and killall5(8) all retrieve a process list and
> kill them one by one, instead of calling kill(-1, signal), so a race
> condition can happen thats let some process escape the final SIGKILL.
> Since pkill(1) a
On Wed, Mar 20, 2019 at 01:14:39PM +0800, Casper Ti. Vector wrote:
> Fixed (provided that sysvinit killall(8) is included in the container)
> in commit 3f246b20 the day before yesterday :)
I forgot to note that sending SIGHUP is unnecessary, and `rc.halt' did
this previously because of my misunder
On Tue, Mar 19, 2019 at 04:58:53PM +0100, Oliver Schad wrote:
> Exactly - it doesn't make sense for us to have for every service it's
> own logging user. So I defined a common log user.
Using separate logging users is mainly due to security reasons: though
s6-log is very reliable, reasonably more
On Tue, 19 Mar 2019 20:42:39 +0800
"Casper Ti. Vector" wrote:
> On Sun, Mar 17, 2019 at 03:30:02PM +0100, Oliver Schad wrote:
> > https://gitlab-2.asag.io/snippets/7
>
> A closer look at this snippet reveals that most changes therein are:
> 1. Customisations of `s6-log.rc', probably modifying
On Tue, Mar 19, 2019 at 08:42:39PM +0800, Casper Ti. Vector wrote:
> * The most important ancillary files are preprocessing passes like
> `misc/openvpn/70-openvpn.rc', which should of course be installed into
> /etc/slew/lib/prep. They are not directly put into `lib/prep' because
> unlike ex
On Sun, Mar 17, 2019 at 03:30:02PM +0100, Oliver Schad wrote:
> https://gitlab-2.asag.io/snippets/7
A closer look at this snippet reveals that most changes therein are:
1. Customisations of `s6-log.rc', probably modifying the logging user.
2. Addition of unshipped services (eg. postfix).
3. Deleti
On Mon, Mar 18, 2019 at 10:44:43PM +0800, Casper Ti. Vector wrote:
> * Transfer the `pkgs' directory (with its contents, all produced in the
> step above) to the Ubuntu VM, run (as root) attached `slew-build.sh'
> in the directory where `pkgs' reside.
Here I actually meant `ubuntu-conf.sh' ins
On Sun, Mar 17, 2019 at 03:30:02PM +0100, Oliver Schad wrote:
> So in the end Slew was great to understand, how s6 could be integrated
> as a pattern. But the units/scripts itself didn't work for us.
I personally use Alpine for servers and Void for desktops, and so did
not know what problems distr
Hi Casper,
thanks for the project. I have to say, that I didn't get really, that
the implementation of jobs is a goal of slew, because most jobs
didn't fit for us.
So I understood the whole project as a nice integration layer for s6,
but we changed every unit, changed reboot, halt, the build-scri
Since the first announcement [1] of slew [2], a few people expressed
interest in the project, but I have received little feedback regarding
its technical contents. Therefore although I have successfully deployed
slew on a few real-life systems, it is still quite a slowly moving
personal hobby proj
11 matches
Mail list logo
