On Fri, Apr 21, 2017 at 5:42 PM, Joel Rees wrote:
On Sat, Apr 22, 2017 at 4:13 AM, Nicholas Geovanis
wrote:
> Like numerous linux users I have sometimes lamented coming to terms with
> systemd. My belief is that it's a well-written collection of software
which
> is somewhat over-engineered. It f
On Sat, Apr 22, 2017 at 4:13 AM, Nicholas Geovanis
wrote:
> Like numerous linux users I have sometimes lamented coming to terms with
> systemd. My belief is that it's a well-written collection of software which
> is somewhat over-engineered. It fills a need, sure, though I've managed to
> live an
Like numerous linux users I have sometimes lamented coming to terms with
systemd. My belief is that it's a well-written collection of software which
is somewhat over-engineered. It fills a need, sure, though I've managed to
live and work without it for a long time (been using linux since 1994). And
On Fri, Apr 14, 2017 at 03:17:00PM +0200, Nicolas George wrote:
> Note: systemd is not for end-users, it is for system administrator and
> distribution authors.
{systemctl,journalctl,etc.} --user beg to differ.
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland
⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net
⠈⠳⣄ Please do not
Greg Wooledge mailto:wooledg%40eeg.ccf.org>> wrote:
On Fri, Apr 14, 2017 at 03:17:00PM +0200, Nicolas George wrote:
> Le quintidi 25 germinal, an CCXXV, Greg Wooledge a écrit :
> > Some day there will be actual end-user-friendly systemd documentation
> > somewhere, consolidating all of these piec
On Fri, Apr 14, 2017 at 9:37 PM, Greg Wooledge wrote:
> [...]
>Don't even get me started on sshd.service vs. ssh.service. Do you
>have any idea how hard it is to notice that extra/missing "d", and
>figure out why things Simply Do Not Work?
Well, that demonstrates that the concept of
Greg Wooledge:
> Don't even get me started on sshd.service vs. ssh.service. Do
> you have any idea how hard it is to notice that extra/missing “d”,
> and figure out why things Simply Do Not Work?
* http://www.mail-archive.com/supervision@list.skarnet.org/msg01486.html
* https://unix.stackexcha
Greg Wooledge [2017-04-14 08:37:55-04] wrote:
> Some day there will be actual end-user-friendly systemd documentation
> somewhere, consolidating all of these pieces of wisdom together. I
> hope.
I learnd by reading systemd's really good man pages:
$ man systemd.unit
$ man systemd.timer
On 14/04/17 14:17, Nicolas George wrote:
Le quintidi 25 germinal, an CCXXV, Greg Wooledge a écrit :
Some day there will be actual end-user-friendly systemd documentation
somewhere, consolidating all of these pieces of wisdom together. I hope.
Note: systemd is not for end-users, it is for syst
On Fri, Apr 14, 2017 at 03:17:00PM +0200, Nicolas George wrote:
> Le quintidi 25 germinal, an CCXXV, Greg Wooledge a écrit :
> > Some day there will be actual end-user-friendly systemd documentation
> > somewhere, consolidating all of these pieces of wisdom together. I hope.
>
> Note: systemd is
On 14-04-17, Nicolas George wrote:
> Le quintidi 25 germinal, an CCXXV, Greg Wooledge a écrit :
> > Some day there will be actual end-user-friendly systemd documentation
> > somewhere, consolidating all of these pieces of wisdom together. I hope.
>
> Note: systemd is not for end-users, it is for
Le quintidi 25 germinal, an CCXXV, Greg Wooledge a écrit :
> Some day there will be actual end-user-friendly systemd documentation
> somewhere, consolidating all of these pieces of wisdom together. I hope.
Note: systemd is not for end-users, it is for system administrator and
distribution authors
On Thu, Apr 13, 2017 at 10:01:25PM +0100, Jonathan de Boyne Pollard wrote:
> ... albeit poorly. If one wants to run daemontools under systemd, svscanboot
> is
> not the way; svscanboot is a thing of the past
> http://jdebp.eu./FGA/inittab-is-history.html#svscanboot , and was a source of
> problem
Greg Wooledge:
>
> Suppose you want to start DJB's daemontools from a locally created systemd
> unit/service. Here's a file that will do that:
>
... albeit poorly. If one wants to run daemontools under systemd, svscanboot is
not the way; svscanboot is a thing of the past
http://jdebp.eu./F
Kevin O'Gorman wrote:
> Are you sure? On my system, this produces nothing at all. But the
> directory
> exists and is populated.
It works great in jessie
$ systemd --version
systemd 215
+PAM +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL
+XZ -SECCOMP -APPARMOR
On Mon, Apr 03, 2017 at 09:36:16AM -0500, Tom Browder wrote:
> But I kind of understand why systemd, but I wish I could find a good
> cookbook description of how to add or modify a new process.
I like the "systemd vs. sysvinit" cheatsheet at
http://linoxide.com/linux-command/systemd-vs-sysvinit-ch
On Mon, Apr 3, 2017 at 10:14 AM, Kevin O'Gorman wrote:
>
>> To see a list of your available targets (assuming no major local changes),
>> use this command:
>>
>> $ find /lib/systemd/ -name '*.target'
>>
>>
> Are you sure? On my system, this produces nothing at all. But the
> directory
> exists
Greg Wooledge [2017-04-03 11:39:42-04] wrote:
> To see a list of your available targets (assuming no major local
> changes), use this command:
>
> $ find /lib/systemd/ -name '*.target'
Often these are useful too:
systemctl -t target list-units
systemctl -t target list-unit-files
--
///
On Mon, Apr 3, 2017 at 8:39 AM, Greg Wooledge wrote:
> On Mon, Apr 03, 2017 at 09:36:16AM -0500, Tom Browder wrote:
> > But I kind of understand why systemd, but I wish I could find a good
> > cookbook description of how to add or modify a new process.
>
> The first hurdle is learning the termino
On Mon, Apr 03, 2017 at 09:36:16AM -0500, Tom Browder wrote:
> But I kind of understand why systemd, but I wish I could find a good
> cookbook description of how to add or modify a new process.
The first hurdle is learning the terminology that systemd uses. It's
not exactly intuitive.
Systemd ha
20 matches
Mail list logo
