[opensuse] Should cron write in upper or lower case?
Since we switched to cronie in openSUSE 11.4, cron has been writing logmessages with the name of the executable in upper case, where as the previous cron daemon wrote in lower case. I opened: https://bugzilla.novell.com/show_bug.cgi?id=780237 Vojtech (the maintainer) doesn't think this regression should be fixed, and closed it as WONTFIX. I think this regression should be fixed, even if nobody else has noticed it in 11.4 and 12.1. Does anyone here have any thoughts on the matter? To me, it's clearly a regression and wrong - the executable name is logged as /USR/SBIN/CRON, which doesn't exist: ls -l /USR/SBIN/CRON ls: cannot access /USR/SBIN/CRON: No such file or directory I discovered it by accident when I upgraded a system to 12.2, but it's been like this for 11.4 and 12.1. -- Per Jessen, Zürich (17.1°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-09-28 15:50, Per Jessen wrote:
Does anyone here have any thoughts on the matter? To me, it's clearly a regression and wrong - the executable name is logged as /USR/SBIN/CRON, which doesn't exist:
Yes, I agree with you, the path and name should be the real one with its real case, not changed to uppercase. - -- Cheers / Saludos, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBlr2UACgkQIvFNjefEBxpUhgCgmKkJXGhhI2z9fp1bZDQxJQ+h TYsAnR2ELKr9+TYf5GbgIUWW2GPmEKIG =og1S -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, Sep 28, 2012 at 03:50:25PM +0200, Per Jessen wrote:
Since we switched to cronie in openSUSE 11.4, cron has been writing logmessages with the name of the executable in upper case, where as the previous cron daemon wrote in lower case.
I opened: https://bugzilla.novell.com/show_bug.cgi?id=3D780237
Vojtech (the maintainer) doesn't think this regression should be fixed, and closed it as WONTFIX. I think this regression should be fixed, even if nobody else has noticed it in 11.4 and 12.1.
Does anyone here have any thoughts on the matter? To me, it's clearly a regression and wrong - the executable name is logged as /USR/SBIN/CRON, which doesn't exist:
ls -l /USR/SBIN/CRON ls: cannot access /USR/SBIN/CRON: No such file or directory
It's to determine if a log message is caused by a child process or from the daemon. It looks like our man page is not up to date. As this has not been noticed for two full release cycles the issue can't be this important. Reverting the change without any further discussion with the cron autors I consider as the wrong approach. Wontfix might not be the correct resolution reason. I consider this a feature and not a bug. Please feel free to file a submit request to enhance the documentation/ man page. Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
Lars Müller wrote:
On Fri, Sep 28, 2012 at 03:50:25PM +0200, Per Jessen wrote:
Since we switched to cronie in openSUSE 11.4, cron has been writing logmessages with the name of the executable in upper case, where as the previous cron daemon wrote in lower case.
I opened: https://bugzilla.novell.com/show_bug.cgi?id=3D780237
Vojtech (the maintainer) doesn't think this regression should be fixed, and closed it as WONTFIX. I think this regression should be fixed, even if nobody else has noticed it in 11.4 and 12.1.
Does anyone here have any thoughts on the matter? To me, it's clearly a regression and wrong - the executable name is logged as /USR/SBIN/CRON, which doesn't exist:
ls -l /USR/SBIN/CRON ls: cannot access /USR/SBIN/CRON: No such file or directory
It's to determine if a log message is caused by a child process or from the daemon.
It looks like our man page is not up to date.
As this has not been noticed for two full release cycles the issue can't be this important.
Reverting the change without any further discussion with the cron autors I consider as the wrong approach.
Why? Like you say, it's clearly not very important when it's been overlooked for so long. I'll fix it myself if I need to, I just don't want to get it done only for Vojtech to reject my patch. Btw, debian bug#15258 dealt with this back in 1997. "cron shouts..." http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=15258 -- Per Jessen, Zürich (18.0°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 9/28/2012 11:02 AM, Lars Müller wrote:
On Fri, Sep 28, 2012 at 03:50:25PM +0200, Per Jessen wrote:
Since we switched to cronie in openSUSE 11.4, cron has been writing logmessages with the name of the executable in upper case, where as the previous cron daemon wrote in lower case.
I opened: https://bugzilla.novell.com/show_bug.cgi?id=3D780237
Vojtech (the maintainer) doesn't think this regression should be fixed, and closed it as WONTFIX. I think this regression should be fixed, even if nobody else has noticed it in 11.4 and 12.1.
Does anyone here have any thoughts on the matter? To me, it's clearly a regression and wrong - the executable name is logged as /USR/SBIN/CRON, which doesn't exist:
ls -l /USR/SBIN/CRON ls: cannot access /USR/SBIN/CRON: No such file or directory
It's to determine if a log message is caused by a child process or from the daemon.
Such an indication is a fine idea. Doing it by lying is not. Add markup characters or something but don't write untruths.
It looks like our man page is not up to date.
As this has not been noticed for two full release cycles the issue can't be this important.
Well, no, the release cycles are idiotically short now, and just because people haven't bothered to report a problem, or that a problem hasn't actually been severe enough to kill a baby, does not mean it's fine to just leave something knowingly broken. For my part, my systems have been running well enough that I haven't had occasion lately to read my logs. Only when I have some reason to even read the logs would I discover that they contained lies. When that happened, maybe I still wouldn't report it because maybe I have other things to do that day and maybe I've been discouraged by previous experiences exactly like this where reported problems were disregarded.
Reverting the change without any further discussion with the cron autors I consider as the wrong approach.
No you need to do _both_ that's why we have such a great patch maintenance system via obs and spec files. Until upstream fixes it, we fix it for ourselves just like we do countless other things, or we don't use that upstream package in the first place since it has broken behavior and that broken behavior is not even considered broken by the author, therefore will never be fixed and we don't want to maintain custom patches forever if we can avoid it.
Wontfix might not be the correct resolution reason. I consider this a feature and not a bug.
Please feel free to file a submit request to enhance the documentation/ man page.
Even if the documentation does not describe the purpose of this behavior, it's still not primarily a documentation error. -- bkw -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 9/28/2012 9:50 AM, Per Jessen wrote:
Since we switched to cronie in openSUSE 11.4, cron has been writing logmessages with the name of the executable in upper case, where as the previous cron daemon wrote in lower case.
I opened: https://bugzilla.novell.com/show_bug.cgi?id=780237
Vojtech (the maintainer) doesn't think this regression should be fixed, and closed it as WONTFIX. I think this regression should be fixed, even if nobody else has noticed it in 11.4 and 12.1.
Does anyone here have any thoughts on the matter? To me, it's clearly a regression and wrong - the executable name is logged as /USR/SBIN/CRON, which doesn't exist:
ls -l /USR/SBIN/CRON ls: cannot access /USR/SBIN/CRON: No such file or directory
I discovered it by accident when I upgraded a system to 12.2, but it's been like this for 11.4 and 12.1.
I consider it wrong and I don't consider that an "opinion" it's a simple observable fact. The unix filesystem is case-sensitive and /USR/BIN/CRON is a pure fiction and toupper()-ing the binary name means the log can no longer distinguish between foo Foo FOo FOO fOO foO fOo FoO. Logs that lie. BRILLIANT. -- bkw -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen said the following on 09/28/2012 09:50 AM:
Does anyone here have any thoughts on the matter? To me, it's clearly a regression and wrong - the executable name is logged as /USR/SBIN/CRON, which doesn't exist:
ls -l /USR/SBIN/CRON ls: cannot access /USR/SBIN/CRON: No such file or directory
I discovered it by accident when I upgraded a system to 12.2, but it's been like this for 11.4 and 12.1.
I think you are missing a point here. "A" point, I say, perhaps not "THE" point, but ... The "/USR/SBIN/CRON" is where its announcing the service reporting. The executable - what cron is running, is in lower case. The mistake here is not that CRON is shouting its name but that its shouting its path. Other entries in syslog look like nmbd[2733]: Got SIGHUP dumping debug info. and pulseaudio[7486]: [pulseaudio] main.c: Daemon startup failed. By comparison, my mailhub server, which runs Mandriva, shouts like this CROND[6594]: (anton) CMD ((fetchmail -q; sleep 5; fetchmail -d 600)) But the whole thing is inconsistent. When I list and then edit my crontab file it is sysloged like this crontab[6550]: (anton) LIST (anton) crontab[6553]: (anton) BEGIN EDIT (anton) crontab[6553]: (anton) REPLACE (anton) crontab[6553]: (anton) END EDIT (anton) crond[1844]: (anton) RELOAD (/var/spool/cron/anton) So yes, having "/USR/SBIN/CRON" is inconsistent. Personally I think the "uppercase path" argument isn't the one to make. That I see nothing else in my syslog that "shouts" and nothing else where the reporting server tells its path (rather than the path of what it is using as an argument). I would base the bug report and request for change on that and not on the fact that "/USR/SBIN/CRON" doesn't exist. -- All warfare is based on deception. There is no place where espionage is not used. Offer the enemy bait to lure him. Sun-Tzu -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anton Aylward wrote:
Per Jessen said the following on 09/28/2012 09:50 AM:
Does anyone here have any thoughts on the matter? To me, it's clearly a regression and wrong - the executable name is logged as /USR/SBIN/CRON, which doesn't exist:
ls -l /USR/SBIN/CRON ls: cannot access /USR/SBIN/CRON: No such file or directory
I discovered it by accident when I upgraded a system to 12.2, but it's been like this for 11.4 and 12.1.
I think you are missing a point here. "A" point, I say, perhaps not "THE" point, but ...
The "/USR/SBIN/CRON" is where its announcing the service reporting. The executable - what cron is running, is in lower case.
The mistake here is not that CRON is shouting its name but that its shouting its path. Other entries in syslog look like
nmbd[2733]: Got SIGHUP dumping debug info. and pulseaudio[7486]: [pulseaudio] main.c: Daemon startup failed.
By comparison, my mailhub server, which runs Mandriva, shouts like this CROND[6594]: (anton) CMD ((fetchmail -q; sleep 5; fetchmail -d 600))
But the whole thing is inconsistent. When I list and then edit my crontab file it is sysloged like this
crontab[6550]: (anton) LIST (anton) crontab[6553]: (anton) BEGIN EDIT (anton) crontab[6553]: (anton) REPLACE (anton) crontab[6553]: (anton) END EDIT (anton) crond[1844]: (anton) RELOAD (/var/spool/cron/anton)
So yes, having "/USR/SBIN/CRON" is inconsistent.
Personally I think the "uppercase path" argument isn't the one to make.
Nor do I, I think "regression" ought to suffice, but it hasn't with the maintainer so far.
That I see nothing else in my syslog that "shouts" and nothing else where the reporting server tells its path (rather than the path of what it is using as an argument). I would base the bug report and request for change on that and not on the fact that "/USR/SBIN/CRON" doesn't exist.
Please amend the bugreport. -- Per Jessen, Zürich (12.6°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, Sep 28, 2012 at 09:29:53PM +0200, Per Jessen wrote:
Anton Aylward wrote: [ 8< ]
Personally I think the "uppercase path" argument isn't the one to make.
Nor do I, I think "regression" ought to suffice, but it hasn't with the maintainer so far.
Have you filed a defect report for screen too? Screen does somethng like cron too. And I'm sure the authors will have a good reason to do so. Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
Lars Müller wrote:
On Fri, Sep 28, 2012 at 09:29:53PM +0200, Per Jessen wrote:
Anton Aylward wrote: [ 8< ]
Personally I think the "uppercase path" argument isn't the one to make.
Nor do I, I think "regression" ought to suffice, but it hasn't with the maintainer so far.
Have you filed a defect report for screen too?
No, I don't think I've ever used screen.
Screen does somethng like cron too. And I'm sure the authors will have a good reason to do so.
I'm sure they do, but has it's behaviour changed? cron has used lowercase at least since SuSE Linux 7.x, then it was changed to uppercase in openSUSE 11.4. cron in SLE uses lowercase too. -- Per Jessen, Zürich (13.4°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, Sep 29, 2012 at 10:30:47AM +0200, Per Jessen wrote:
Lars Müller wrote:
On Fri, Sep 28, 2012 at 09:29:53PM +0200, Per Jessen wrote:
Anton Aylward wrote: [ 8< ]
Personally I think the "uppercase path" argument isn't the one to make.
Nor do I, I think "regression" ought to suffice, but it hasn't with the maintainer so far.
Have you filed a defect report for screen too?
No, I don't think I've ever used screen.
Screen does somethng like cron too. And I'm sure the authors will have a good reason to do so.
I'm sure they do, but has it's behaviour changed?
And such a change is not allowed? If they have a good reason such a change must be possible.
cron has used lowercase at least since SuSE Linux 7.x, then it was changed to uppercase in openSUSE 11.4. cron in SLE uses lowercase too.
You can't compare openSUSE with SUSE Linux Enterprise (SLE). BTW which version you talk about and which Service Pack (SP) level? SLE 11 and all later SPs have a base close to openSUSE 11.1. Check this version and check which cron had been part of this. Then go from version to version and compare the change logs of the included cron package. If you see a defect go with it to the upstream issue tracker and report the URL to the mailing list archive or the issue tracker back to this list. This is not a SUSE issue. This is a cron issue you should report to the cron developers. That Debian reverted the change is no argument. Read the defect report. There are no arguments in the report. There is only the patch to revert the behavior to the previous one. Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
Lars Müller wrote:
On Sat, Sep 29, 2012 at 10:30:47AM +0200, Per Jessen wrote:
Lars Müller wrote:
On Fri, Sep 28, 2012 at 09:29:53PM +0200, Per Jessen wrote:
Anton Aylward wrote: [ 8< ]
Personally I think the "uppercase path" argument isn't the one to make.
Nor do I, I think "regression" ought to suffice, but it hasn't with the maintainer so far.
Have you filed a defect report for screen too?
No, I don't think I've ever used screen.
Screen does somethng like cron too. And I'm sure the authors will have a good reason to do so.
I'm sure they do, but has it's behaviour changed?
And such a change is not allowed?
If they have a good reason such a change must be possible.
Of course, but I have not heard anyone explain why it was changed. That's why I call it a regression.
cron has used lowercase at least since SuSE Linux 7.x, then it was changed to uppercase in openSUSE 11.4. cron in SLE uses lowercase too.
You can't compare openSUSE with SUSE Linux Enterprise (SLE).
Why not? They're just two Linux'es that behave differently.
BTW which version you talk about and which Service Pack (SP) level?
None in particular, it's not important in this context as I'm pretty certain they all have a cron that writes in lower case.
SLE 11 and all later SPs have a base close to openSUSE 11.1. Check this version and check which cron had been part of this. Then go from version to version and compare the change logs of the included cron package.
If you see a defect go with it to the upstream issue tracker and report the URL to the mailing list archive or the issue tracker back to this list.
This is not a SUSE issue. This is a cron issue you should report to the cron developers.
Lars, don't be a jerk. I am reporting the bug in our project because the regression took place in our project. -- Per Jessen, Zürich (13.2°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, Sep 29, 2012 at 02:17:42PM +0200, Per Jessen wrote:
Lars Müller wrote:
On Sat, Sep 29, 2012 at 10:30:47AM +0200, Per Jessen wrote:
Lars Müller wrote:
On Fri, Sep 28, 2012 at 09:29:53PM +0200, Per Jessen wrote:
Anton Aylward wrote: [ 8< ]
Personally I think the "uppercase path" argument isn't the one to make.
Nor do I, I think "regression" ought to suffice, but it hasn't with the maintainer so far.
Have you filed a defect report for screen too?
No, I don't think I've ever used screen.
Screen does somethng like cron too. And I'm sure the authors will have a good reason to do so.
I'm sure they do, but has it's behaviour changed?
And such a change is not allowed?
If they have a good reason such a change must be possible.
Of course, but I have not heard anyone explain why it was changed. That's why I call it a regression.
cron has used lowercase at least since SuSE Linux 7.x, then it was changed to uppercase in openSUSE 11.4. cron in SLE uses lowercase too.
You can't compare openSUSE with SUSE Linux Enterprise (SLE).
Why not? They're just two Linux'es that behave differently. o
I've written why it is how it is. I described it. Nothing more. There is nothing to discuss from the openSUSE side. If this change didn't cause any trouble and has not been seen for several years this is much noise about nothing.
BTW which version you talk about and which Service Pack (SP) level?
None in particular, it's not important in this context as I'm pretty certain they all have a cron that writes in lower case.
As I wrote before: It's a much older code base and therefore you compare apples with peaches.
SLE 11 and all later SPs have a base close to openSUSE 11.1. Check this version and check which cron had been part of this. Then go from version to version and compare the change logs of the included cron package.
If you see a defect go with it to the upstream issue tracker and report the URL to the mailing list archive or the issue tracker back to this list.
This is not a SUSE issue. This is a cron issue you should report to the cron developers.
Lars, don't be a jerk. I am reporting the bug in our project because the regression took place in our project.
Then you have to stand up and to maintain cron and the required patches and have to be the default defect owner. I'm going to drink a coffee. That's of more value. Thanks, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-09-29 14:54, Lars Müller wrote:
On Sat, Sep 29, 2012 at 02:17:42PM +0200, Per Jessen wrote:
And such a change is not allowed?
If they have a good reason such a change must be possible.
Of course, but I have not heard anyone explain why it was changed. That's why I call it a regression.
I have not seen yet an explanation of what we gain.
If this change didn't cause any trouble and has not been seen for several years this is much noise about nothing.
No. I saw it time ago, and I wanted to ask about it. But I had bigger issues at the time and it slipped my mind. - -- Cheers / Saludos, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBm/BkACgkQIvFNjefEBxrMtwCffq1XK4Q2pjduCXo2t84YT17g Ky4AoIqdrqDWUiZkK1aTrXzW6WE6jXcu =P1EH -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-09-29 14:54, Lars Müller wrote:
On Sat, Sep 29, 2012 at 02:17:42PM +0200, Per Jessen wrote:
And such a change is not allowed?
If they have a good reason such a change must be possible.
Of course, but I have not heard anyone explain why it was changed. That's why I call it a regression.
I have not seen yet an explanation of what we gain.
[again, sorry about the late response, the thread got lost in my reader] cronie is probably(!) newer/better/prettier than vixie-cron, which I assume is why we moved. As always with openSUSE, the reasoning is not always clear. I have no issues with the move at all, except this one regression. -- Per Jessen, Zürich (16.7°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Lars Müller wrote:
On Sat, Sep 29, 2012 at 02:17:42PM +0200, Per Jessen wrote:
Lars Müller wrote:
On Sat, Sep 29, 2012 at 10:30:47AM +0200, Per Jessen wrote:
Lars Müller wrote:
On Fri, Sep 28, 2012 at 09:29:53PM +0200, Per Jessen wrote:
Anton Aylward wrote: [ 8< ] > Personally I think the "uppercase path" argument isn't the > one to make.
Nor do I, I think "regression" ought to suffice, but it hasn't with the maintainer so far.
Have you filed a defect report for screen too?
No, I don't think I've ever used screen.
Screen does somethng like cron too. And I'm sure the authors will have a good reason to do so.
I'm sure they do, but has it's behaviour changed?
And such a change is not allowed?
If they have a good reason such a change must be possible.
Of course, but I have not heard anyone explain why it was changed. That's why I call it a regression.
cron has used lowercase at least since SuSE Linux 7.x, then it was changed to uppercase in openSUSE 11.4. cron in SLE uses lowercase too.
You can't compare openSUSE with SUSE Linux Enterprise (SLE).
Why not? They're just two Linux'es that behave differently. o
I've written why it is how it is. I described it. Nothing more.
[sorry about the late response, your reply got lost somewhere.] Well, same here - and as we are just plain community members both of us, neither is right nor wrong.
There is nothing to discuss from the openSUSE side.
How do you know that, you're just another community member, don't pretend you're something else. Or do you believe you're something different?
If this change didn't cause any trouble and has not been seen for several years this is much noise about nothing.
Lars, try this http://www.dict.cc/?s=several
BTW which version you talk about and which Service Pack (SP) level?
None in particular, it's not important in this context as I'm pretty certain they all have a cron that writes in lower case.
As I wrote before: It's a much older code base and therefore you compare apples with peaches.
So why did you bother asking asking about wich service pack level?
SLE 11 and all later SPs have a base close to openSUSE 11.1. Check this version and check which cron had been part of this. Then go from version to version and compare the change logs of the included cron package.
If you see a defect go with it to the upstream issue tracker and report the URL to the mailing list archive or the issue tracker back to this list.
This is not a SUSE issue. This is a cron issue you should report to the cron developers.
Lars, don't be a jerk. I am reporting the bug in our project because the regression took place in our project.
Then you have to stand up and to maintain cron and the required patches and have to be the default defect owner.
Sure, I don't mind. Where/how do I sign up to be the maintainer of cronie? -- Per Jessen, Zürich (16.7°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, Oct 06, 2012 at 10:16:57PM +0200, Per Jessen wrote:
Lars Müller wrote:
On Sat, Sep 29, 2012 at 02:17:42PM +0200, Per Jessen wrote: [ 8< ] Then you have to stand up and to maintain cron and the required patches and have to be the default defect owner.
Sure, I don't mind. Where/how do I sign up to be the maintainer of cronie?
To get a maintainer of a component depends on how the maintership of the particular software piece is organized. As cron has an active maintainer I would expect you contribute and by this show your comitment and then the current maintainer might share the position with you. But this depends on the particular software component. As I've not worked on cron you must discuss this with the maintainer(s) of the component. With Samba for example I would expect some upstream activity and some active contribution to our packages. With cron this might be different. I expect it's not this simple as you might have guessed based on my reply. Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
participants (5)
-
Anton Aylward -
Brian K. White -
Carlos E. R. -
Lars Müller -
Per Jessen