I ran into a problem in OpenSuSE 15.5 trying to start the cron.service daemon. It failed because the directory at /etc/cron.d was empty (which in previous releases of OpenSuSE it was not empty). The cron.service file, as supplied from the installation repos, has a couple of ExecStartPre shell commands shown here - (the second ExecStartPre command seems to be redundant, but I don't know that for sure, because I don't know how chmod is suppose to handle recursion and wildchars. Man pages seem unclear about this). ExecStartPre=+/bin/sh -c '/bin/chmod -R 0744 /etc/cron.*' # Only do the following ExecStartPre if there is something in /etc/cron.d ExecStartPre=+/bin/sh -c '/bin/chmod -R 0644 /etc/cron.d/*' Even commenting out the second ExecStartPre command doesn't solve the failure I was getting from the first chmod command. Anywise I managed to fix this issue by using the following ExecStartPre commands instead - ExecStartPre=+/bin/sh -c '/bin/chmod 0744 /etc/cron.*' ExecStartPre=+/bin/sh -c '/bin/chmod -R 0744 /etc/cron.*/*' So, is the script in cron.service wrong/broken or is chmod itself broken? (or maybe my version of OpenSuSE 15.5 is screwed up somehow? won't be the first thing to have gone wrong with it on my new laptop! sigh) Marc...
On Fri, Feb 9, 2024 at 11:11 AM Marc Chamberlin via openSUSE Users <users@lists.opensuse.org> wrote:
I ran into a problem in OpenSuSE 15.5 trying to start the cron.service daemon. It failed because the directory at /etc/cron.d was empty (which in previous releases of OpenSuSE it was not empty). The cron.service file, as supplied from the installation repos, has a couple of ExecStartPre shell commands shown here - (the second ExecStartPre command seems to be redundant, but I don't know that for sure, because I don't know how chmod is suppose to handle recursion and wildchars. Man pages seem unclear about this).
You neither tell what package you installed nor show the actual errors. IIRC Leap is using cronie and its cron.service does not have these commands.
ExecStartPre=+/bin/sh -c '/bin/chmod -R 0744 /etc/cron.*' # Only do the following ExecStartPre if there is something in /etc/cron.d ExecStartPre=+/bin/sh -c '/bin/chmod -R 0644 /etc/cron.d/*'
Even commenting out the second ExecStartPre command doesn't solve the failure I was getting from the first chmod command. Anywise I managed to fix this issue by using the following ExecStartPre commands instead -
ExecStartPre=+/bin/sh -c '/bin/chmod 0744 /etc/cron.*' ExecStartPre=+/bin/sh -c '/bin/chmod -R 0744 /etc/cron.*/*'
So, is the script in cron.service wrong/broken or is chmod itself broken? (or maybe my version of OpenSuSE 15.5 is screwed up somehow? won't be the first thing to have gone wrong with it on my new laptop! sigh)
Marc...
Please keep in mind that many of the members on this list are older and may no longer have pristine vision which makes reading your HTML messages with a tiny font difficult to read. Ken Schneider
On Feb 9, 2024, at 3:19 AM, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
On Fri, Feb 9, 2024 at 11:11 AM Marc Chamberlin via openSUSE Users <users@lists.opensuse.org> wrote:
I ran into a problem in OpenSuSE 15.5 trying to start the cron.service daemon. It failed because the directory at /etc/cron.d was empty (which in previous releases of OpenSuSE it was not empty). The cron.service file, as supplied from the installation repos, has a couple of ExecStartPre shell commands shown here - (the second ExecStartPre command seems to be redundant, but I don't know that for sure, because I don't know how chmod is suppose to handle recursion and wildchars. Man pages seem unclear about this).
You neither tell what package you installed nor show the actual errors. IIRC Leap is using cronie and its cron.service does not have these commands.
ExecStartPre=+/bin/sh -c '/bin/chmod -R 0744 /etc/cron.*' # Only do the following ExecStartPre if there is something in /etc/cron.d ExecStartPre=+/bin/sh -c '/bin/chmod -R 0644 /etc/cron.d/*'
Even commenting out the second ExecStartPre command doesn't solve the failure I was getting from the first chmod command. Anywise I managed to fix this issue by using the following ExecStartPre commands instead -
ExecStartPre=+/bin/sh -c '/bin/chmod 0744 /etc/cron.*' ExecStartPre=+/bin/sh -c '/bin/chmod -R 0744 /etc/cron.*/*'
So, is the script in cron.service wrong/broken or is chmod itself broken? (or maybe my version of OpenSuSE 15.5 is screwed up somehow? won't be the first thing to have gone wrong with it on my new laptop! sigh)
Marc...
On 2/9/24 06:49, kschneider bout-tyme.net wrote:
Please keep in mind that many of the members on this list are older and may no longer have pristine vision which makes reading your HTML messages with a tiny font difficult to read. Ken Schneider
Ken - we could start a whole new thread talking about how bad and f&*%ked up handling fonts/font sizes in OpenSuSE is! Apparently what looked good to me when I send emails does not end up looking good to the receiver. There are so many font management tools, both discoverable and undiscoverable, versions, and even applications with their own font management tools, (Thunderbird, my email client that I use, for example) that I wince every time I try to manage fonts and I just hate it. I STILL have lots of stuff that I cannot figure out how to manage the fonts for, and for the most part I just have to live with what I get. Nor is it possible to keep track (automate) of who wants HTML v.s. plain text emails so I end up letting Thunderbird handle that in it's own automagic way. Try using Cntl + to enlarge the font in your email client the next time you get something that is unreadable. That works for a lot of apps, but not all. Marc...
On 2024-02-09 20:00, Marc Chamberlin via openSUSE Users wrote:
On 2/9/24 06:49, kschneider bout-tyme.net wrote:
Please keep in mind that many of the members on this list are older and may no longer have pristine vision which makes reading your HTML messages with a tiny font difficult to read. Ken Schneider
Ken - we could start a whole new thread talking about how bad and f&*%ked up handling fonts/font sizes in OpenSuSE is! Apparently what looked good to me when I send emails does not end up looking good to the receiver. There are so many font management tools, both discoverable and undiscoverable, versions, and even applications with their own font management tools, (Thunderbird, my email client that I use, for example) that I wince every time I try to manage fonts and I just hate it. I STILL have lots of stuff that I cannot figure out how to manage the fonts for, and for the most part I just have to live with what I get.
In this case, it is your fault, sorry :-) Thunderbird can write in these font sizes: T Larger (size 6). T Larger (size 5) T Larger (size 4) T Normal font. T Smaller (size 2) T Smaller (size 1) Your text used size 1 for the paragraph, and size two for the command line text. What font is actually used is selected by the recipient software, but the sender chooses the relative size. Just type your message in what Thunderbird says it is "normal size" and the receiver should be fine. If the "normal size" seems too big at your side, then change the font size in preferences of TB. But do not type your letter choosing "smaller" or "double smaller" unless you want to type the fine print of a legal document ;-) -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On Fri, 9 Feb 2024 20:57:34 +0100 "Carlos E.R. via openSUSE Users" <users@lists.opensuse.org> wrote: [snip the whole debate] ... better yet, post plain text emails instead of the HTML nonsense! :) BTW, font sizes are measured in points, not in arbitrary "Thunderbird units" :(
Dave Howorth composed on 2024-02-09 20:38 (UTC):
On Fri, 9 Feb 2024 20:57:34 +0100 Carlos E.R. wrote: [snip the whole debate]
... better yet, post plain text emails instead of the HTML nonsense! :)
BTW, font sizes are measured in points, not in arbitrary "Thunderbird units" :(
Traditionally, absolutely; but the web is anything but traditional. W3C standards ejected appropriate use of pt around a decade ago. Now to conform to "standards", web browsers must insanely equate points to pixels on a 1:1 basis. Font sizes in *current* Mozilla products are measured and defined in pixels, not points. :( -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El 2024-02-09 a las 20:38 -0000, Dave Howorth escribió:
On Fri, 9 Feb 2024 20:57:34 +0100 "Carlos E.R. via openSUSE Users" <...> wrote:
[snip the whole debate]
... better yet, post plain text emails instead of the HTML nonsense! :)
BTW, font sizes are measured in points, not in arbitrary "Thunderbird units" :(
Look at the actual message code: </blockquote> In this case, it is your fault, sorry :-)<br> <br> Thunderbird can write in these font sizes:<br> <blockquote><font size=3D"6">T=C2=A0=C2=A0=C2=A0 Larger (size 6).</font><br> <font size=3D"5">T=C2=A0=C2=A0=C2=A0 Larger (size 5)</font><br> <font size=3D"4">T=C2=A0=C2=A0=C2=A0 Larger (size 4)</font><br> T=C2=A0=C2=A0=C2=A0 Normal font.<br> <font size=3D"2">T=C2=A0=C2=A0=C2=A0 Smaller (size 2)</font><br> <font size=3D"1">T=C2=A0=C2=A0=C2=A0 Smaller (size 1)</font><font size=3D"6"><br> </font></blockquote> - -- Cheers, Carlos E. R. (from openSUSE 15.4 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCZcaUTRwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVU7oAn3cCVxrNPjdKezyRxrXq E6ffjVdXAJ90lvdOJi9QgbbHUY4FPjL7ZqB9MA== =RdGr -----END PGP SIGNATURE-----
Carlos E. R. composed on 2024-02-09 22:08 (UTC+0100):
Look at the actual message code:
</blockquote> In this case, it is your fault, sorry :-)<br> <br> Thunderbird can write in these font sizes:<br> <blockquote><font size=3D"6">T=C2=A0=C2=A0=C2=A0 Larger (size 6).</font><br> <font size=3D"5">T=C2=A0=C2=A0=C2=A0 Larger (size 5)</font><br> <font size=3D"4">T=C2=A0=C2=A0=C2=A0 Larger (size 4)</font><br> T=C2=A0=C2=A0=C2=A0 Normal font.<br> <font size=3D"2">T=C2=A0=C2=A0=C2=A0 Smaller (size 2)</font><br> <font size=3D"1">T=C2=A0=C2=A0=C2=A0 Smaller (size 1)</font><font size=3D"6"><br> </font></blockquote>
Translation of named/numbered sizes in legacy web browsers using default settings and the standard arbitrary DPI assumption of 96 (factual physically on a ~13.5" screen with resolution of 1024x768; or a ~23" 1920x1080 screen; 12pt=16px): 7 = xx-large = 32px = 24.00pt 6 = x-large = 24px = 18.00pt 5 = large = 18px = 13.50pt 4 = medium = 16px = 12.00pt 3 = small = 13px = 9.75pt 2 = x-small = 10px = 7.50pt 1 = xx-small = 9px = 6.75pt Many moons ago I tried to get the differences between sizes to be less disparate proportionally, but gave up after 7 years getting nowhere: https://bugzilla.mozilla.org/show_bug.cgi?id=187256 Most newer browsers read/produce pt settings as though they were px settings, a 1:1 ratio instead of the variable ratios that physically exist when taking into account real display density (measured in DPI/dots per inch). Why Carlos is showing 3 as "normal" I don't grok. I use SeaMonkey, and don't ever compose email using HTML except under extreme duress. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 2024-02-10 01:42, Felix Miata wrote:
Carlos E. R. composed on 2024-02-09 22:08 (UTC+0100):
Look at the actual message code:
</blockquote> In this case, it is your fault, sorry :-)<br> <br> Thunderbird can write in these font sizes:<br> <blockquote><font size=3D"6">T=C2=A0=C2=A0=C2=A0 Larger (size 6).</font><br> <font size=3D"5">T=C2=A0=C2=A0=C2=A0 Larger (size 5)</font><br> <font size=3D"4">T=C2=A0=C2=A0=C2=A0 Larger (size 4)</font><br> T=C2=A0=C2=A0=C2=A0 Normal font.<br> <font size=3D"2">T=C2=A0=C2=A0=C2=A0 Smaller (size 2)</font><br> <font size=3D"1">T=C2=A0=C2=A0=C2=A0 Smaller (size 1)</font><font size=3D"6"><br> </font></blockquote>
Translation of named/numbered sizes in legacy web browsers using default settings and the standard arbitrary DPI assumption of 96 (factual physically on a ~13.5" screen with resolution of 1024x768; or a ~23" 1920x1080 screen; 12pt=16px):
7 = xx-large = 32px = 24.00pt 6 = x-large = 24px = 18.00pt 5 = large = 18px = 13.50pt 4 = medium = 16px = 12.00pt 3 = small = 13px = 9.75pt 2 = x-small = 10px = 7.50pt 1 = xx-small = 9px = 6.75pt
Many moons ago I tried to get the differences between sizes to be less disparate proportionally, but gave up after 7 years getting nowhere: https://bugzilla.mozilla.org/show_bug.cgi?id=187256
Most newer browsers read/produce pt settings as though they were px settings, a 1:1 ratio instead of the variable ratios that physically exist when taking into account real display density (measured in DPI/dots per inch).
Well, but this is the mail client, not the web browser. The mail composer has a few settings in the tool bar to choose sizes or styles. The rest is hidden in the menu.
Why Carlos is showing 3 as "normal" I don't grok. I use SeaMonkey, and don't ever compose email using HTML except under extreme duress.
Well, try it and find out what it does :-) It is Thunderbird who says that size 3 is "normal", not me. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
I no longer use my laptop for reading email, it’s getting old like me and I no longer have a need to buy a replacement. So I use the email client on my iPad 4 gen 6 which does not, to my knowledge, have a way to alter font sizes. Sorry for the noise. Staying subscribed to this list after nearly 30 years helps me pass the time and stay in touch with the openSUSE crowd. Ken Schneider On Feb 9, 2024, at 2:57 PM, Carlos E.R. via openSUSE Users <users@lists.opensuse.org> wrote: On 2024-02-09 20:00, Marc Chamberlin via openSUSE Users wrote: On 2/9/24 06:49, kschneider bout-tyme.net wrote: Please keep in mind that many of the members on this list are older and may no longer have pristine vision which makes reading your HTML messages with a tiny font difficult to read. Ken Schneider Ken - we could start a whole new thread talking about how bad and f&*%ked up handling fonts/font sizes in OpenSuSE is! Apparently what looked good to me when I send emails does not end up looking good to the receiver. There are so many font management tools, both discoverable and undiscoverable, versions, and even applications with their own font management tools, (Thunderbird, my email client that I use, for example) that I wince every time I try to manage fonts and I just hate it. I STILL have lots of stuff that I cannot figure out how to manage the fonts for, and for the most part I just have to live with what I get. In this case, it is your fault, sorry :-) Thunderbird can write in these font sizes: T Larger (size 6). T Larger (size 5) T Larger (size 4) T Normal font. T Smaller (size 2) T Smaller (size 1) Your text used size 1 for the paragraph, and size two for the command line text. What font is actually used is selected by the recipient software, but the sender chooses the relative size. Just type your message in what Thunderbird says it is "normal size" and the receiver should be fine. If the "normal size" seems too big at your side, then change the font size in preferences of TB. But do not type your letter choosing "smaller" or "double smaller" unless you want to type the fine print of a legal document ;-) -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 2024-02-09 23:05, kschneider bout-tyme.net wrote:
I no longer use my laptop for reading email, it’s getting old like me and I no longer have a need to buy a replacement. So I use the email client on my iPad 4 gen 6 which does not, to my knowledge, have a way to alter font sizes.
You do not have to alter sizes. I said that it is Marc who has to do it and I explained how. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
* Carlos E.R. via openSUSE Users <users@lists.opensuse.org> [02-09-24 17:25]:
On 2024-02-09 23:05, kschneider bout-tyme.net wrote:
I no longer use my laptop for reading email, it’s getting old like me and I no longer have a need to buy a replacement. So I use the email client on my iPad 4 gen 6 which does not, to my knowledge, have a way to alter font sizes.
You do not have to alter sizes. I said that it is Marc who has to do it and I explained how.
he really does not. the solution that will provide a satisfactory display is to use *text* as email list are intended. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
* Marc Chamberlin via openSUSE Users <users@lists.opensuse.org> [02-09-24 14:00]:
On 2/9/24 06:49, kschneider bout-tyme.net wrote:
Please keep in mind that many of the members on this list are older and may no longer have pristine vision which makes reading your HTML messages with a tiny font difficult to read. Ken Schneider
Ken - we could start a whole new thread talking about how bad and f&*%ked up handling fonts/font sizes in OpenSuSE is! Apparently what looked good to me when I send emails does not end up looking good to the receiver. There are so many font management tools, both discoverable and undiscoverable, versions, and even applications with their own font management tools, (Thunderbird, my email client that I use, for example) that I wince every time I try to manage fonts and I just hate it. I STILL have lots of stuff that I cannot figure out how to manage the fonts for, and for the most part I just have to live with what I get.
Nor is it possible to keep track (automate) of who wants HTML v.s. plain text emails so I end up letting Thunderbird handle that in it's own automagic way.
much better and more satisfying to default to lowest possible denominator which is "plain text".
Try using Cntl + to enlarge the font in your email client the next time you get something that is unreadable. That works for a lot of apps, but not all.
Marc...
BEGIN:VCARD VERSION:4.0 N:Chamberlin;Marc;;; NICKNAME:Marc EMAIL;PREF=1;TYPE=home:marc@marcchamberlin.com TEL;TYPE=home;VALUE=TEXT:360-835-8184 TEL;TYPE=cell;VALUE=TEXT:503-522-3703 URL;TYPE=home:https://www.marcchamberlin.com URL;TYPE=home:https://www.domesweetdome.us.com NOTE:Attached is my public key for encrypting email you wish to send to me. EMAIL;TYPE=home:marc@domesweetdome.us.com EMAIL:eveningdarkstar@gmail.com END:VCARD
you have a particular reason for wanting the entire world to know your "vcard" ??? it's just more irrelevant posting and distracting from the true purpose of your original post. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
* Marc Chamberlin via openSUSE Users<users@lists.opensuse.org> [02-09-24 14:00]:
On 2/9/24 06:49, kschneider bout-tyme.net wrote:
Please keep in mind that many of the members on this list are older and may no longer have pristine vision which makes reading your HTML messages with a tiny font difficult to read. Ken Schneider
Ken - we could start a whole new thread talking about how bad and f&*%ked up handling fonts/font sizes in OpenSuSE is! Apparently what looked good to me when I send emails does not end up looking good to the receiver. There are so many font management tools, both discoverable and undiscoverable, versions, and even applications with their own font management tools, (Thunderbird, my email client that I use, for example) that I wince every time I try to manage fonts and I just hate it. I STILL have lots of stuff that I cannot figure out how to manage the fonts for, and for the most part I just have to live with what I get.
Nor is it possible to keep track (automate) of who wants HTML v.s. plain text emails so I end up letting Thunderbird handle that in it's own automagic way.
much better and more satisfying to default to lowest possible denominator which is "plain text". Getting a bit off-topic now, but Thunderbird use to have a way of associating what kind of email a recipient wanted, HTML v.s. plain text. I wonder why that feature went away, would sure make handling things
On 2/9/24 12:06, Patrick Shanahan wrote: like replies/messages to mail list groups much easier!
you have a particular reason for wanting the entire world to know your "vcard" ???
it's just more irrelevant posting and distracting from the true purpose of your original post.
Oops! Sorry, forgot that vcard attachment was turned on, I want it on for some "official" business communication I do with lawyers and accountants, but not for mail lists. Like the HTML v.s. plain text issue, I wish Thunderbird had the ability to turn on or off signatures, v-cards, encryption, signing etc., based on who the recipient is. One size does not fit all, as the saying goes and from what I see Thunderbird's design team is lousy at doing use case studies... Marc...
* Marc Chamberlin via openSUSE Users <users@lists.opensuse.org> [02-09-24 16:43]:
On 2/9/24 12:06, Patrick Shanahan wrote:
* Marc Chamberlin via openSUSE Users<users@lists.opensuse.org> [02-09-24 14:00]:
On 2/9/24 06:49, kschneider bout-tyme.net wrote:
Please keep in mind that many of the members on this list are older and may no longer have pristine vision which makes reading your HTML messages with a tiny font difficult to read. Ken Schneider
Ken - we could start a whole new thread talking about how bad and f&*%ked up handling fonts/font sizes in OpenSuSE is! Apparently what looked good to me when I send emails does not end up looking good to the receiver. There are so many font management tools, both discoverable and undiscoverable, versions, and even applications with their own font management tools, (Thunderbird, my email client that I use, for example) that I wince every time I try to manage fonts and I just hate it. I STILL have lots of stuff that I cannot figure out how to manage the fonts for, and for the most part I just have to live with what I get.
Nor is it possible to keep track (automate) of who wants HTML v.s. plain text emails so I end up letting Thunderbird handle that in it's own automagic way.
much better and more satisfying to default to lowest possible denominator which is "plain text". Getting a bit off-topic now, but Thunderbird use to have a way of associating what kind of email a recipient wanted, HTML v.s. plain text. I wonder why that feature went away, would sure make handling things like replies/messages to mail list groups much easier! you have a particular reason for wanting the entire world to know your "vcard" ???
it's just more irrelevant posting and distracting from the true purpose of your original post. Oops! Sorry, forgot that vcard attachment was turned on, I want it on for some "official" business communication I do with lawyers and accountants, but not for mail lists. Like the HTML v.s. plain text issue, I wish Thunderbird had the ability to turn on or off signatures, v-cards, encryption, signing etc., based on who the recipient is. One size does not fit all, as the saying goes and from what I see Thunderbird's design team is lousy at doing use case studies...
*YOU* have chosen to use thunderbird which you cannot control or doesn't have the abilities you desire. either bad choice or lack of knowledge of your chosen apps or ... but it is not thunderbird's problem. it's your choice. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
From: Andrei Borzenkov <arvidjaar@gmail.com> Date: Fri, 9 Feb 2024 11:19:23 +0300 On Fri, Feb 9, 2024 at 11:11 AM Marc Chamberlin via openSUSE Users <users@lists.opensuse.org> wrote:
I ran into a problem in OpenSuSE 15.5 trying to start the cron.service daemon. It failed because the directory at /etc/cron.d was empty . . .
You neither tell what package you installed nor show the actual errors. IIRC Leap is using cronie and its cron.service does not have these commands. I am running 15.5 and its /usr/lib/systemd/system/cron.service (currently owned by cronie-1.5.7-150400.84.3.1.x86_64) also has no ExecStartPre commands. -- Bob Rogers http://www.rgrjr.com/
On Fri, Feb 9, 2024 at 11:11 AM Marc Chamberlin via openSUSE Users <users@lists.opensuse.org> wrote:
I ran into a problem in OpenSuSE 15.5 trying to start the cron.service daemon. It failed because the directory at /etc/cron.d was empty (which in previous releases of OpenSuSE it was not empty). The cron.service file, as supplied from the installation repos, has a couple of ExecStartPre shell commands shown here - (the second ExecStartPre command seems to be redundant, but I don't know that for sure, because I don't know how chmod is suppose to handle recursion and wildchars. Man pages seem unclear about this).
You neither tell what package you installed nor show the actual errors. IIRC Leap is using cronie and its cron.service does not have these commands. Sorry, I didn't know that there were multiple packages that install cron.service and it's unreasonable that you expected me to report what
On 2/9/24 00:19, Andrei Borzenkov wrote: package I installed. I thought it was sufficient to simply report that I am running OpenSuSE 15.5 and whatever package(s) for cron were installed by default. Anywise, I see that both the cron and the cronie packages are installed on my laptop (I wish Yast had a better way to export this information) - cron - Auxiliary package Alternate Version Installed Version Version: 4.2-150400.84.3.1 4.2-150400.84.3.1 Build Time: Wed 18 Jan 2023 01:38:41 AM PST Wed 18 Jan 2023 01:38:41 AM PST Install Time: Mon 11 Dec 2023 07:17:38 AM PST License: BSD-3-Clause AND GPL-2.0-only AND MIT BSD-3-Clause AND GPL-2.0-only AND MIT Installed Size: 181 B 181 B Download Size: 17.5 KiB 0 B Distribution: SUSE Linux Enterprise 15 Vendor: SUSE LLC <https://www.suse.com/> SUSE LLC <https://www.suse.com/> Packager: https://www.suse.com/ https://www.suse.com/ Architecture: x86_64 x86_64 Build Host: sheep52 sheep52 URL: https://github.com/cronie-crond/cronie https://github.com/cronie-crond/cronie Source Package: cronie-1.5.7-150400.84.3.1 cronie-1.5.7-150400.84.3.1 Media No.: 1 0 Authors: cronie - Cron Daemon Alternate Version Installed Version Version: 1.5.7-150400.84.3.1 1.5.7-150400.84.3.1 Build Time: Wed 18 Jan 2023 01:38:41 AM PST Wed 18 Jan 2023 01:38:41 AM PST Install Time: Mon 11 Dec 2023 07:17:38 AM PST License: BSD-3-Clause AND GPL-2.0-only AND MIT BSD-3-Clause AND GPL-2.0-only AND MIT Installed Size: 313.7 KiB 313.7 KiB Download Size: 117.0 KiB 0 B Distribution: SUSE Linux Enterprise 15 Vendor: SUSE LLC <https://www.suse.com/> SUSE LLC <https://www.suse.com/> Packager: https://www.suse.com/ https://www.suse.com/ Architecture: x86_64 x86_64 Build Host: sheep52 sheep52 URL: https://github.com/cronie-crond/cronie https://github.com/cronie-crond/cronie Source Package: cronie-1.5.7-150400.84.3.1 cronie-1.5.7-150400.84.3.1 Media No.: 1 0 Authors: Oh brother! Apparently after rebooting my laptop this morning I can't reproduce the error without commenting out the last ExecStartPre command as directed by the comment just above it. (I had commented it out, before reporting this problem yesterday, and was still getting the same error, hence my wondering if chmod was broken.) As for the actual error reported, it was pretty straightforward - systemctl status cron × cron.service - Command Scheduler Loaded: loaded (/etc/systemd/system/cron.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2024-02-09 10:09:25 PST; 29s ago Process: 10176 ExecStartPre=/bin/sh -c /bin/chmod -R 0744 /etc/cron.* (code=exited, status=0/SUCCESS) Process: 10177 ExecStartPre=/bin/sh -c /bin/chmod -R 0644 /etc/cron.d/* (code=exited, status=1/FAILURE) Feb 09 10:09:25 wa7pxw systemd[1]: Starting Command Scheduler... Feb 09 10:09:25 wa7pxw sh[10177]: /bin/chmod: cannot access '/etc/cron.d/*': No such file or directory Feb 09 10:09:25 wa7pxw systemd[1]: cron.service: Control process exited, code=exited, status=1/FAILURE Feb 09 10:09:25 wa7pxw systemd[1]: cron.service: Failed with result 'exit-code'. Feb 09 10:09:25 wa7pxw systemd[1]: Failed to start Command Scheduler. Regardless, I will argue that my way of starting the cron service is better than the way initially provided by the version of cron.service file that I got from the OpenSuSE 15.5 repository. Using my version of the ExecStartPre and chmod commands does not require the user to comment or uncomment anything in the cron.service file. It works regardless of whether the /etc/cron.d directory is empty or not. Marc...
On 09.02.2024 21:36, Marc Chamberlin via openSUSE Users wrote: ...
Loaded: loaded (/etc/systemd/system/cron.service; enabled; vendor preset: enabled)
No package installs units in /etc (at least, should not, and most certainly not cronie). If you believe it was installed by some package - find out which package did it, verify that file is unmodified and file bug report. But most likely you created this file in the past and forgot about it.
Active: failed (Result: exit-code) since Fri 2024-02-09 10:09:25 PST; 29s ago Process: 10176 ExecStartPre=/bin/sh -c /bin/chmod -R 0744 /etc/cron.* (code=exited, status=0/SUCCESS) Process: 10177 ExecStartPre=/bin/sh -c /bin/chmod -R 0644 /etc/cron.d/* (code=exited, status=1/FAILURE)
This is example of pretty optimistic shell programming. You can never be sure there are files matched by expansion pattern and always have to verify you got expected results.
On 2024-02-09 09:10, Marc Chamberlin via openSUSE Users wrote:
I ran into a problem in OpenSuSE 15.5 trying to start the cron.service daemon. It failed because the directory at /etc/cron.d was empty (which in previous releases of OpenSuSE it was not empty). The cron.service file, as supplied from the installation repos,
This phrase makes people think that you installed cron.service manually "somehow", that it is not the default installed file. So, what is the full path of that "cron.service" file? Assuming that it is "/usr/lib/systemd/system/cron.service", then please do: rpm -qf /usr/lib/systemd/system/cron.service rpm -qfi /usr/lib/systemd/system/cron.service systemctl cat cron.service And paste it all into your reply here. Complete, including the initial command prompt, like: cer@Telcontar:~> rpm -qf /usr/lib/systemd/system/cron.service cronie-1.5.7-150400.84.3.1.x86_64 cer@Telcontar:~> -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 2/9/24 10:56, Carlos E. R. wrote:
On 2024-02-09 09:10, Marc Chamberlin via openSUSE Users wrote:
I ran into a problem in OpenSuSE 15.5 trying to start the cron.service daemon. It failed because the directory at /etc/cron.d was empty (which in previous releases of OpenSuSE it was not empty). The cron.service file, as supplied from the installation repos,
This phrase makes people think that you installed cron.service manually "somehow", that it is not the default installed file.
So, what is the full path of that "cron.service" file?
Assuming that it is "/usr/lib/systemd/system/cron.service", then please do:
rpm -qf /usr/lib/systemd/system/cron.service rpm -qfi /usr/lib/systemd/system/cron.service
systemctl cat cron.service
And paste it all into your reply here. Complete, including the initial command prompt, like:
cer@Telcontar:~> rpm -qf /usr/lib/systemd/system/cron.service cronie-1.5.7-150400.84.3.1.x86_64 cer@Telcontar:~>
Carlos, can do, with a bit more info and explanation... wa7pxw:/usr/lib/systemd/system # rpm -qf /usr/lib/systemd/system/cron.service cronie-1.5.7-150400.84.3.1.x86_64 wa7pxw:/usr/lib/systemd/system # rpm -qfi /usr/lib/systemd/system/cron.service Name : cronie Version : 1.5.7 Release : 150400.84.3.1 Architecture: x86_64 Install Date: Mon 11 Dec 2023 07:17:38 AM PST Group : System/Daemons Size : 321186 License : BSD-3-Clause AND GPL-2.0-only AND MIT Signature : RSA/SHA256, Wed 18 Jan 2023 01:39:12 AM PST, Key ID 70af9e8139db7c82 Source RPM : cronie-1.5.7-150400.84.3.1.src.rpm Build Date : Wed 18 Jan 2023 01:38:41 AM PST Build Host : sheep52 Relocations : (not relocatable) Packager : https://www.suse.com/ Vendor : SUSE LLC <https://www.suse.com/> URL : https://github.com/cronie-crond/cronie Summary : Cron Daemon Description : cron automatically starts programs at specific times. Add new entries with "crontab -e". (See "man 5 crontab" and "man 1 crontab" for documentation.) Under /etc, find the directories cron.hourly, cron.daily, cron.weekly, and cron.monthly. Scripts and programs that are located there are started automatically. Distribution: SUSE Linux Enterprise 15 ---- Ok, this next bit that you asked for is showing the version of /etc/systemd/system/cron.service that I created in order to correct the version that was in /usr/lib/systemd/system/cron.service. My modus operandi is that if I have to modify a .service file, I leave the original in /usr/lib/systemd/system and put the modified version in /etc/systemd/system Empirical observations tell me that anything in /etc/systemd/system takes precedence over anything in /usr/lib/systemd/system. I will show the version found at /usr/lib/systemd/system/cron.service below this output - --- wa7pxw:/usr/lib/systemd/system # systemctl cat cron.service # Warning: cron.service changed on disk, the version systemd has loaded is outdated. # This output shows the current version of the unit's original fragment and drop-in files. # If fragments or drop-ins were added or removed, they are not properly reflected in this output. # Run 'systemctl daemon-reload' to reload units. # /etc/systemd/system/cron.service [Unit] Description=Command Scheduler After=nss-user-lookup.target network.target time-sync.target After=postfix.service sendmail.service exim.service [Service] # ExecStartPre=+/bin/sh -c '/bin/chmod -R 0744 /etc/cron.*' ExecStartPre=+/bin/sh -c '/bin/chmod 0744 /etc/cron.*' ExecStartPre=+/bin/sh -c '/bin/chmod -R 0744 /etc/cron.*/*' # Only do the following ExecStartPre if there is something in /etc/cron.d # ExecStartPre=+/bin/sh -c '/bin/chmod -R 0644 /etc/cron.d/*' ExecStartPre=+/bin/chmod 0644 /etc/crontab ExecStart=/usr/sbin/cron -n ExecReload=/usr/bin/kill -s SIGHUP $MAINPID Restart=on-abort KillMode=process TasksMax=infinity [Install] WantedBy=multi-user.target --- wa7pxw:/usr/lib/systemd/system #cat cron.service [Unit] Description=Command Scheduler After=nss-user-lookup.target network.target time-sync.target After=postfix.service sendmail.service exim.service [Service] ExecStartPre=+/bin/sh -c '/bin/chmod -R 0744 /etc/cron.*' # Only do the following ExecStartPre if there is something in /etc/cron.d ExecStartPre=+/bin/sh -c '/bin/chmod -R 0644 /etc/cron.d/*' ExecStartPre=+/bin/chmod 0644 /etc/crontab ExecStart=/usr/sbin/cron -n ExecReload=/usr/bin/kill -s SIGHUP $MAINPID Restart=on-abort KillMode=process TasksMax=infinity [Install] WantedBy=multi-user.target --- I checked back on other systems running OpenSuSE x64 - 15.4, 15.3, 15.2, and 15.0 and found that the version of cron.service in /usr/lib/systemd/system were all identical. So if this is a change that I or one of my co-workers made, then it was done years ago and forgotten about. I can't say nor can I understand how it has propagated through so many upgrades. (some of which I am pretty sure were done as a new installation from a DVD disk, not as an "in-place" upgrade from a previous version)
On 2024-02-09 21:21, Marc Chamberlin via openSUSE Users wrote:
On 2/9/24 10:56, Carlos E. R. wrote:
On 2024-02-09 09:10, Marc Chamberlin via openSUSE Users wrote:
I ran into a problem in OpenSuSE 15.5 trying to start the cron.service daemon. It failed because the directory at /etc/cron.d was empty (which in previous releases of OpenSuSE it was not empty). The cron.service file, as supplied from the installation repos,
This phrase makes people think that you installed cron.service manually "somehow", that it is not the default installed file.
So, what is the full path of that "cron.service" file?
Assuming that it is "/usr/lib/systemd/system/cron.service", then please do:
rpm -qf /usr/lib/systemd/system/cron.service rpm -qfi /usr/lib/systemd/system/cron.service
systemctl cat cron.service
And paste it all into your reply here. Complete, including the initial command prompt, like:
cer@Telcontar:~> rpm -qf /usr/lib/systemd/system/cron.service cronie-1.5.7-150400.84.3.1.x86_64 cer@Telcontar:~>
Carlos, can do, with a bit more info and explanation...
Allow me to reformat your paragraph into "prefeformat" or it is difficult to read:
wa7pxw:/usr/lib/systemd/system # rpm -qf /usr/lib/systemd/system/cron.service cronie-1.5.7-150400.84.3.1.x86_64 wa7pxw:/usr/lib/systemd/system # rpm -qfi /usr/lib/systemd/system/cron.service Name : cronie Version : 1.5.7 Release : 150400.84.3.1 Architecture: x86_64 Install Date: Mon 11 Dec 2023 07:17:38 AM PST Group : System/Daemons Size : 321186 License : BSD-3-Clause AND GPL-2.0-only AND MIT Signature : RSA/SHA256, Wed 18 Jan 2023 01:39:12 AM PST, Key ID 70af9e8139db7c82 Source RPM : cronie-1.5.7-150400.84.3.1.src.rpm Build Date : Wed 18 Jan 2023 01:38:41 AM PST Build Host : sheep52 Relocations : (not relocatable) Packager :https://www.suse.com/ Vendor : SUSE LLC<https://www.suse.com/> URL :https://github.com/cronie-crond/cronie Summary : Cron Daemon Description : cron automatically starts programs at specific times. Add new entries with "crontab -e". (See "man 5 crontab" and "man 1 crontab" for documentation.)
wa7pxw:/usr/lib/systemd/system # rpm -qf /usr/lib/systemd/system/cron.service
cronie-1.5.7-150400.84.3.1.x86_64
wa7pxw:/usr/lib/systemd/system # rpm -qfi /usr/lib/systemd/system/cron.service
Name : cronie
Version : 1.5.7
Release : 150400.84.3.1
Architecture: x86_64
Install Date: Mon 11 Dec 2023 07:17:38 AM PST
Group : System/Daemons
Size : 321186
License : BSD-3-Clause AND GPL-2.0-only AND MIT
Signature : RSA/SHA256, Wed 18 Jan 2023 01:39:12 AM PST, Key ID 70af9e8139db7c82
Source RPM : cronie-1.5.7-150400.84.3.1.src.rpm
Build Date : Wed 18 Jan 2023 01:38:41 AM PST
Build Host : sheep52
Relocations : (not relocatable)
Packager :https://www.suse.com/
Vendor : SUSE LLC<https://www.suse.com/>
URL :https://github.com/cronie-crond/cronie
Summary : Cron Daemon
Description :
cron automatically starts programs at specific times. Add new entries
with "crontab -e". (See "man 5 crontab" and "man 1 crontab" for
documentation.)
Under /etc, find the directories cron.hourly, cron.daily, cron.weekly, and cron.monthly. Scripts and programs that are located there are started automatically. Distribution: SUSE Linux Enterprise 15
Notice that I am not familiar with SLES. I have to assume that it is the same as openSUSE Leap 15.5 or 15.4
---- Ok, this next bit that you asked for is showing the version of /etc/systemd/system/cron.service that I created in order to correct the version that was in /usr/lib/systemd/system/cron.service. My modus operandi is that if I have to modify a .service file, I leave the original in /usr/lib/systemd/system and put the modified version in /etc/systemd/system Empirical observations tell me that anything in /etc/systemd/system takes precedence over anything in /usr/lib/systemd/system.
That's not the way to do it. Instead, you have to run "systemctl edit cron.service". In actual fact, what is edited is file "/etc/systemd/system/cron.service.d/override.conf", which is created automatically.
I will show the version found at /usr/lib/systemd/system/cron.service below this output -
---
wa7pxw:/usr/lib/systemd/system # systemctl cat cron.service # Warning: cron.service changed on disk, the version systemd has loaded is outdated. # This output shows the current version of the unit's original fragment and drop-in files. # If fragments or drop-ins were added or removed, they are not properly reflected in this output. # Run 'systemctl daemon-reload' to reload units. # /etc/systemd/system/cron.service [Unit] Description=Command Scheduler After=nss-user-lookup.target network.target time-sync.target After=postfix.service sendmail.service exim.service
[Service] # ExecStartPre=+/bin/sh -c '/bin/chmod -R 0744 /etc/cron.*'
ExecStartPre=+/bin/sh -c '/bin/chmod 0744 /etc/cron.*' ExecStartPre=+/bin/sh -c '/bin/chmod -R 0744 /etc/cron.*/*'
# Only do the following ExecStartPre if there is something in /etc/cron.d # ExecStartPre=+/bin/sh -c '/bin/chmod -R 0644 /etc/cron.d/*'
ExecStartPre=+/bin/chmod 0644 /etc/crontab ExecStart=/usr/sbin/cron -n ExecReload=/usr/bin/kill -s SIGHUP $MAINPID Restart=on-abort KillMode=process TasksMax=infinity
[Install] WantedBy=multi-user.target
---
Notice that the output is in fact from "/etc/systemd/system/cron.service"
wa7pxw:/usr/lib/systemd/system #cat cron.service [Unit] Description=Command Scheduler After=nss-user-lookup.target network.target time-sync.target After=postfix.service sendmail.service exim.service
[Service] ExecStartPre=+/bin/sh -c '/bin/chmod -R 0744 /etc/cron.*' # Only do the following ExecStartPre if there is something in /etc/cron.d ExecStartPre=+/bin/sh -c '/bin/chmod -R 0644 /etc/cron.d/*'
ExecStartPre=+/bin/chmod 0644 /etc/crontab ExecStart=/usr/sbin/cron -n ExecReload=/usr/bin/kill -s SIGHUP $MAINPID Restart=on-abort KillMode=process TasksMax=infinity
[Install] WantedBy=multi-user.target
--- I checked back on other systems running OpenSuSE x64 - 15.4, 15.3, 15.2, and 15.0 and found that the version of cron.service in /usr/lib/systemd/system were all identical. So if this is a change that I or one of my co-workers made, then it was done years ago and forgotten about. I can't say nor can I understand how it has propagated through so many upgrades. (some of which I am pretty sure were done as a new installation from a DVD disk, not as an "in-place" upgrade from a previous version)
So, you have a modified file. I would delete (or rename) both files and reinstall cron. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
participants (9)
-
Andrei Borzenkov -
Bob Rogers -
Carlos E. R. -
Carlos E.R. -
Dave Howorth -
Felix Miata -
kschneider bout-tyme.net -
Marc Chamberlin -
Patrick Shanahan