Hi all,
So sorry to be late on this. There's a systemd series in the works that we'd like to get people to start working on. Anyone interested in writing one of these? This is a great opportunity to get involved even if you are more of a techie type, and don't want to have to figure out a topic on your own. We've done it for you! :-)
If interested, just reply here on the list. Feel free to reach out to community friends if you know someone who'd be interested, and get them in touch with us.
* * *
systemd part 1: What is a unit file? What kind of things can it do? Where should I modify or put new unit files on my system? How can I find out what unit owns a process now running? How can I really kill all processes for a unit?
systemd part 2: What are unit dependencies? How can you enforce ordering of e.g. daemons or one-shot launches? How does this concept lend to faster boot times?
systemd part 3: How can I more effectively use the systemd journal to find and diagnose problems? [bound by time, by unit, since last boot, other?...]
systemd part 4: How do I convert an existing SysVinit script into a systemd unit file?
systemd part 5: How can I use a template unit file? [an example is the getty service -- perhaps show how to launch multiple web hosts or something this way?]
systemd part 6: How to mask a service unit (and why; difference between this and disable) *** Ashutosh already volunteered for this one! \o/
Heya, You can mark me down for parts 1, 2 and 3
Cheers Bryan On Thu, Oct 8, 2015 at 16:47 Paul W. Frields stickster@gmail.com wrote:
Hi all,
So sorry to be late on this. There's a systemd series in the works that we'd like to get people to start working on. Anyone interested in writing one of these? This is a great opportunity to get involved even if you are more of a techie type, and don't want to have to figure out a topic on your own. We've done it for you! :-)
If interested, just reply here on the list. Feel free to reach out to community friends if you know someone who'd be interested, and get them in touch with us.
systemd part 1: What is a unit file? What kind of things can it do? Where should I modify or put new unit files on my system? How can I find out what unit owns a process now running? How can I really kill all processes for a unit?
systemd part 2: What are unit dependencies? How can you enforce ordering of e.g. daemons or one-shot launches? How does this concept lend to faster boot times?
systemd part 3: How can I more effectively use the systemd journal to find and diagnose problems? [bound by time, by unit, since last boot, other?...]
systemd part 4: How do I convert an existing SysVinit script into a systemd unit file?
systemd part 5: How can I use a template unit file? [an example is the getty service -- perhaps show how to launch multiple web hosts or something this way?]
systemd part 6: How to mask a service unit (and why; difference between this and disable) *** Ashutosh already volunteered for this one! \o/
-- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ The open source story continues to grow: http://opensource.com -- marketing mailing list marketing@lists.fedoraproject.org List info or to change your subscription: https://admin.fedoraproject.org/mailman/listinfo/marketing
On Thu, Oct 08, 2015 at 09:10:17PM +0000, Bryan Sutherland wrote:
On Thu, Oct 8, 2015 at 16:47 Paul W. Frields stickster@gmail.com wrote:
Hi all,
So sorry to be late on this. There's a systemd series in the works that we'd like to get people to start working on. Anyone interested in writing one of these? This is a great opportunity to get involved even if you are more of a techie type, and don't want to have to figure out a topic on your own. We've done it for you! :-)
If interested, just reply here on the list. Feel free to reach out to community friends if you know someone who'd be interested, and get them in touch with us.
systemd part 1: What is a unit file? What kind of things can it do? Where should I modify or put new unit files on my system? How can I find out what unit owns a process now running? How can I really kill all processes for a unit?
systemd part 2: What are unit dependencies? How can you enforce ordering of e.g. daemons or one-shot launches? How does this concept lend to faster boot times?
systemd part 3: How can I more effectively use the systemd journal to find and diagnose problems? [bound by time, by unit, since last boot, other?...]
Heya, You can mark me down for parts 1, 2 and 3
Cheers Bryan
That sounds awesome Bryan. If you wanted to start with part 1, do you think you could draft something by next Tuesday 2015-Oct-13?
You can meet up with us on IRC Freenode #fedora-mktg for some help getting started. Here are some helpful hints:
http://fedoramagazine.org/writing-an-article-for-the-fedora-magazine/
(It looks like you're partway through step 3 already. See one of us on IRC with your username so we can make you an Author.)
Will be Tuesday - Late Tuesday. With that said, can someone please top me up with some editor privileges on the Magazine?
Cheers
On Thu, Oct 8, 2015 at 5:50 PM, Paul W. Frields stickster@gmail.com wrote:
On Thu, Oct 08, 2015 at 09:10:17PM +0000, Bryan Sutherland wrote:
On Thu, Oct 8, 2015 at 16:47 Paul W. Frields stickster@gmail.com
wrote:
Hi all,
So sorry to be late on this. There's a systemd series in the works that we'd like to get people to start working on. Anyone interested in writing one of these? This is a great opportunity to get involved even if you are more of a techie type, and don't want to have to figure out a topic on your own. We've done it for you! :-)
If interested, just reply here on the list. Feel free to reach out to community friends if you know someone who'd be interested, and get them in touch with us.
systemd part 1: What is a unit file? What kind of things can it do? Where should I modify or put new unit files on my system? How can I find out what unit owns a process now running? How can I really kill all processes for a unit?
systemd part 2: What are unit dependencies? How can you enforce ordering of e.g. daemons or one-shot launches? How does this concept lend to faster boot times?
systemd part 3: How can I more effectively use the systemd journal to find and diagnose problems? [bound by time, by unit, since last boot, other?...]
Heya, You can mark me down for parts 1, 2 and 3
Cheers Bryan
That sounds awesome Bryan. If you wanted to start with part 1, do you think you could draft something by next Tuesday 2015-Oct-13?
You can meet up with us on IRC Freenode #fedora-mktg for some help getting started. Here are some helpful hints:
http://fedoramagazine.org/writing-an-article-for-the-fedora-magazine/
(It looks like you're partway through step 3 already. See one of us on IRC with your username so we can make you an Author.)
-- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ The open source story continues to grow: http://opensource.com -- marketing mailing list marketing@lists.fedoraproject.org List info or to change your subscription: https://admin.fedoraproject.org/mailman/listinfo/marketing
On 10/13/2015 03:49 AM, Bryan Sutherland wrote:
Will be Tuesday - Late Tuesday. With that said, can someone please top me up with some editor privileges on the Magazine?
Cheers
I think we got the permissions sorted now via IRC.
I think I have also solved the issue where people with Author status couldnt preview posts. The permission that was not being given to authors was the ability to edit others posts (unpublished). I have fixed this now, and authors should be able to preview posts in the meetings :)
cheers, ryanlerch
On Tue, Oct 13, 2015 at 01:49:32PM +1000, Ryan Lerch wrote:
On 10/13/2015 03:49 AM, Bryan Sutherland wrote:
Will be Tuesday - Late Tuesday. With that said, can someone please top me up with some editor privileges on the Magazine?
Cheers
I think we got the permissions sorted now via IRC.
I think I have also solved the issue where people with Author status couldnt preview posts. The permission that was not being given to authors was the ability to edit others posts (unpublished). I have fixed this now, and authors should be able to preview posts in the meetings :)
Thanks for doing this, Ryan.
On Wed, Oct 14, 2015 at 5:35 PM, Paul W. Frields stickster@gmail.com wrote:
On Tue, Oct 13, 2015 at 01:49:32PM +1000, Ryan Lerch wrote:
On 10/13/2015 03:49 AM, Bryan Sutherland wrote:
Will be Tuesday - Late Tuesday. With that said, can someone please top
me
up with some editor privileges on the Magazine?
Cheers
I think we got the permissions sorted now via IRC.
I think I have also solved the issue where people with Author status
couldnt
preview posts. The permission that was not being given to authors was the ability to edit others posts (unpublished). I have fixed this now, and authors should be able to preview posts in the meetings :)
Thanks for doing this, Ryan.
Hey Ryan, The first draft of the Part 2 article has been posted up. There is still some work to do though :)
FYI, you can find my article scribbles here: https://pagure.io/fmag-articles
I love this idea. I'm interested in doing #5, this is something that has been super useful for me
On Wed, 14 Oct 2015 at 17:59 Bryan Sutherland bryan.sutherland@gmail.com wrote:
On Wed, Oct 14, 2015 at 5:35 PM, Paul W. Frields stickster@gmail.com wrote:
On Tue, Oct 13, 2015 at 01:49:32PM +1000, Ryan Lerch wrote:
On 10/13/2015 03:49 AM, Bryan Sutherland wrote:
Will be Tuesday - Late Tuesday. With that said, can someone please
top me
up with some editor privileges on the Magazine?
Cheers
I think we got the permissions sorted now via IRC.
I think I have also solved the issue where people with Author status
couldnt
preview posts. The permission that was not being given to authors was
the
ability to edit others posts (unpublished). I have fixed this now, and authors should be able to preview posts in the meetings :)
Thanks for doing this, Ryan.
Hey Ryan, The first draft of the Part 2 article has been posted up. There is still some work to do though :)
FYI, you can find my article scribbles here: https://pagure.io/fmag-articles%E2%80%8B
-- marketing mailing list marketing@lists.fedoraproject.org List info or to change your subscription: https://admin.fedoraproject.org/mailman/listinfo/marketing
On Wed, Oct 14, 2015 at 10:12:41PM +0000, Chaoyi Zha wrote:
I love this idea. I'm interested in doing #5, this is something that has been super useful for me
Hi Chaoyi[*],
Please feel free to start drafting this as soon as you like. We are setting up due dates for the series and I'll post those to the list, too.
If you find you don't have access needed to start, please let us know by email here, or by visiting #fedora-mktg on IRC Freenode.
* * * [*] I sometimes mistake the order of given name vs. surname for some locales. If I got yours wrong, please forgive me and feel free to correct me!
Hi Paul,
No worries. I'll start writing a draft soon and will pitch it next week.
Thanks
On Fri, Oct 16, 2015, 11:18 AM Paul W. Frields stickster@gmail.com wrote:
On Wed, Oct 14, 2015 at 10:12:41PM +0000, Chaoyi Zha wrote:
I love this idea. I'm interested in doing #5, this is something that has been super useful for me
Hi Chaoyi[*],
Please feel free to start drafting this as soon as you like. We are setting up due dates for the series and I'll post those to the list, too.
If you find you don't have access needed to start, please let us know by email here, or by visiting #fedora-mktg on IRC Freenode.
[*] I sometimes mistake the order of given name vs. surname for some locales. If I got yours wrong, please forgive me and feel free to correct me!
-- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ The open source story continues to grow: http://opensource.com -- marketing mailing list marketing@lists.fedoraproject.org List info or to change your subscription: https://admin.fedoraproject.org/mailman/listinfo/marketing
On Thu, Oct 8, 2015 at 4:47 PM, Paul W. Frields stickster@gmail.com wrote:
systemd part 4: How do I convert an existing SysVinit script into a systemd unit file?
If no one is yet doing this (it seems not from the thread, could be wrong) I'd be interested in writing this.I'll draft something up in the next few hours, but I don't have author permissions. If someone could set me up (jstanley) that'd be awesome. I've already logged into Wordpress so my account should be there.
On 10/18/2015 04:08 AM, Jon Stanley wrote:
On Thu, Oct 8, 2015 at 4:47 PM, Paul W. Frields stickster@gmail.com wrote:
systemd part 4: How do I convert an existing SysVinit script into a systemd unit file?
If no one is yet doing this (it seems not from the thread, could be wrong) I'd be interested in writing this.I'll draft something up in the next few hours, but I don't have author permissions. If someone could set me up (jstanley) that'd be awesome. I've already logged into Wordpress so my account should be there.
Someone must have already granted you access -- you are listed as an author, so you should be able to edit away!
cheers, ryanlerch
On Mon, Oct 19, 2015 at 12:40 AM, Ryan Lerch rlerch@redhat.com wrote:
Someone must have already granted you access -- you are listed as an author, so you should be able to edit away!
Cool, thanks! Apparently that is now part 5. Can someone take a look and make sure that I'm on the right track here? It's slightly more than I thought that it would be, since I'm going into fairly considerable detail. Some of it may be covered by other parts of the series, and some may just be me pontificating on how great systemd is :). I just want to make sure general style is OK before I flesh out other parts of the article.
On Tue, Oct 20, 2015 at 12:34:31AM -0400, Jon Stanley wrote:
On Mon, Oct 19, 2015 at 12:40 AM, Ryan Lerch rlerch@redhat.com wrote:
Someone must have already granted you access -- you are listed as an author, so you should be able to edit away!
Cool, thanks! Apparently that is now part 5. Can someone take a look and make sure that I'm on the right track here? It's slightly more than I thought that it would be, since I'm going into fairly considerable detail. Some of it may be covered by other parts of the series, and some may just be me pontificating on how great systemd is :). I just want to make sure general style is OK before I flesh out other parts of the article.
Hi Jon,
I took a look and I liked the way it was going. It's a difficult topic, easy to get complex quickly. We have a while before this one will come up for final review, so if you don't mind, I'll do a more thorough feedback in a little bit. :-)
On Mon, Oct 26, 2015 at 11:41:06PM -0400, Paul W. Frields wrote:
On Tue, Oct 20, 2015 at 12:34:31AM -0400, Jon Stanley wrote:
On Mon, Oct 19, 2015 at 12:40 AM, Ryan Lerch rlerch@redhat.com wrote:
Someone must have already granted you access -- you are listed as an author, so you should be able to edit away!
Cool, thanks! Apparently that is now part 5. Can someone take a look and make sure that I'm on the right track here? It's slightly more than I thought that it would be, since I'm going into fairly considerable detail. Some of it may be covered by other parts of the series, and some may just be me pontificating on how great systemd is :). I just want to make sure general style is OK before I flesh out other parts of the article.
Hi Jon,
I took a look and I liked the way it was going. It's a difficult topic, easy to get complex quickly. We have a while before this one will come up for final review, so if you don't mind, I'll do a more thorough feedback in a little bit. :-)
Jon, can we consider using this for next week's series entry?
On Thu, Oct 29, 2015 at 6:07 PM, Paul W. Frields stickster@gmail.com wrote:
Jon, can we consider using this for next week's series entry?
Blergh, baseball and life caught up with me! I somehow didn't even see this email (which is somewhat unusual for me....) until now. Probably not this week, but I'll put some time into it this week since it still needs A LOT more work before I consider it complete.
On Mon, Nov 02, 2015 at 02:01:11AM -0500, Jon Stanley wrote:
On Thu, Oct 29, 2015 at 6:07 PM, Paul W. Frields stickster@gmail.com wrote:
Jon, can we consider using this for next week's series entry?
Blergh, baseball and life caught up with me! I somehow didn't even see this email (which is somewhat unusual for me....) until now. Probably not this week, but I'll put some time into it this week since it still needs A LOT more work before I consider it complete.
Because we planned to have this ready for publication this Wednesday, I finished a revision this morning. Jon, can you check it and see if you like where it went?
I also made a graphic for it over the weekend.
On Mon, Nov 2, 2015 at 12:22 PM, Paul W. Frields stickster@gmail.com wrote:
Because we planned to have this ready for publication this Wednesday, I finished a revision this morning. Jon, can you check it and see if you like where it went?
I also made a graphic for it over the weekend.
Looks awesome! Sorry that I couldn't take this one to the finish line :(
One technical quibble - EnvironmentFile is *not* just like the old SysV init - there you could execute any code of your choosing (though most didn't do that, IIRC there was one or two init scripts that I recall that took advantage of that fact). In systemd you're restricted to key/value pairs in there.
Other than that looks great!
On Mon, Nov 2, 2015 at 1:29 PM, Jon Stanley jonstanley@gmail.com wrote:
Other than that looks great!
Oops, one more - KillMode=process is important for sshd, but probably not for 99.9% of other units, so it was probably a bad choice to examine. What it really does is when you stop it, systemd only terminates the main PID, and not any children that may be in the same cgroup. For sshd, this is critical since if you are connecting via ssh, and do 'systemctl stop sshd.service', then your session would die since it would kill everything in the cgroup.
I'm not certain if we want to get into details like that in this post (it's somewhat esoteric), but it is critically important IMO to understanding how systemd uses cgroups to group processes and optionally apply resource controls to them.
On Mon, Nov 02, 2015 at 01:34:57PM -0500, Jon Stanley wrote:
On Mon, Nov 2, 2015 at 1:29 PM, Jon Stanley jonstanley@gmail.com wrote:
Other than that looks great!
Oops, one more - KillMode=process is important for sshd, but probably not for 99.9% of other units, so it was probably a bad choice to examine. What it really does is when you stop it, systemd only terminates the main PID, and not any children that may be in the same cgroup. For sshd, this is critical since if you are connecting via ssh, and do 'systemctl stop sshd.service', then your session would die since it would kill everything in the cgroup.
I'm not certain if we want to get into details like that in this post (it's somewhat esoteric), but it is critically important IMO to understanding how systemd uses cgroups to group processes and optionally apply resource controls to them.
We haven't gone deeply into cgroups and I was thinking of saving that for an additional post. But this is probably something that can be explained in simple terms in the article, as you've explained it quite well here. The fact that it's an abnormal usage is not necessarily a terrible choice.
On Tue, Nov 3, 2015 at 3:29 PM, Paul W. Frields stickster@gmail.com wrote:
On Mon, Nov 02, 2015 at 01:34:57PM -0500, Jon Stanley wrote:
On Mon, Nov 2, 2015 at 1:29 PM, Jon Stanley jonstanley@gmail.com wrote:
Other than that looks great!
Oops, one more - KillMode=process is important for sshd, but probably not for 99.9% of other units, so it was probably a bad choice to examine. What it really does is when you stop it, systemd only terminates the main PID, and not any children that may be in the same cgroup. For sshd, this is critical since if you are connecting via ssh, and do 'systemctl stop sshd.service', then your session would die since it would kill everything in the cgroup.
I'm not certain if we want to get into details like that in this post (it's somewhat esoteric), but it is critically important IMO to understanding how systemd uses cgroups to group processes and optionally apply resource controls to them.
We haven't gone deeply into cgroups and I was thinking of saving that for an additional post. But this is probably something that can be explained in simple terms in the article, as you've explained it quite well here. The fact that it's an abnormal usage is not necessarily a terrible choice.
I made all the changes Jon noted. This article is ready to go.
marketing@lists.fedoraproject.org
-
Bryan Sutherland -
Chaoyi Zha -
Jon Stanley -
Jon Stanley -
Paul W. Frields -
Ryan Lerch