I've had SuSE 10 installed on my HP box for roughly a week, now, and cron has yet to do the job regarding the daily stuff, at least. I tried the hourly and it, too, seemed not to notice. At least that one appeared in the logs but nothing happened --i.e., #logrotate /etc/logrotate --force-- and it should have happened for the simple reason that issuing that command by hand does rotate the logs. Anyone else having cron problems?? I remember on other time, on either 9.1,.2., or .3 when I had the same problem (but I didn't stay with any of them long enough to figure it out as too much other stuff was busted). Thanks! -- ...Yogich
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2005-11-17 at 13:39 -0600, Yogich wrote:
Anyone else having cron problems?? I remember on other time, on either
I suppose you have got all YOU patches? There must have been a few, but I can't say if they apply to your problem. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDfRhWtTMYHG2NR9URAuLsAJ98ff7mQy3VIDVFojFhj/3ucsNGSACfaJGD oChnAthzne0Vm3NUoPtcg5s= =bWQQ -----END PGP SIGNATURE-----
On Thursday 17 November 2005 17:54, Carlos E. R. wrote:
The Thursday 2005-11-17 at 13:39 -0600, Yogich wrote:
Anyone else having cron problems?? I remember on other time, on either
I suppose you have got all YOU patches? There must have been a few, but I can't say if they apply to your problem.
-- Cheers, Carlos Robinson
I learned the hard way --and over several distros-- that one doesn't apply updates to this box unless one wants the distro to break. Of course, I still try, sometimes, and inevitably end up dragging out the backup I made before I began. Remember the busted ppp I told you about in 9.1,.2 & .3? All of it caused by updates?? That's why I tend to yawn when one mentions them. ;-) -- ...Yogich
Yogich, On Thursday 17 November 2005 20:13, Yogich wrote:
On Thursday 17 November 2005 17:54, Carlos E. R. wrote:
The Thursday 2005-11-17 at 13:39 -0600, Yogich wrote:
Anyone else having cron problems?? I remember on other time, on either
I suppose you have got all YOU patches? There must have been a few, but I can't say if they apply to your problem.
-- Cheers, Carlos Robinson
I learned the hard way --and over several distros-- that one doesn't apply updates to this box unless one wants the distro to break.
Bah! Maybe other, inferior distributions cannot maintain the integrity of their software in the face necessary upgrades (for security vulnerabilities or other bug fixes), but that is most certainly not the case with SuSE. You'd do well to run SuSE Watcher, checking for updates on the default interval, and apply all critical updates that become available. I've got to say, all the superstition people bring to IT really bugs me.
Of course, I still try, sometimes, and inevitably end up dragging out the backup I made before I began. Remember the busted ppp I told you about in 9.1,.2 & .3? All of it caused by updates??
Highly unlikely.
That's why I tend to yawn when one mentions them. ;-) --
Then you should not expect to get effective help from people who recognize and accept the passage of time and the ongoing improvement of the software packages they use.
...Yogich
Randall Schulz
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2005-11-17 at 20:30 -0800, Randall R Schulz wrote:
Of course, I still try, sometimes, and inevitably end up dragging out the backup I made before I began. Remember the busted ppp I told you about in 9.1,.2 & .3? All of it caused by updates??
Highly unlikely.
I remember he had problem after some updates, we talked about them here at the time. Some of those problems I had as well: pppd was certainly broken in 9.1, and got solved in 9.3. Nevertheless, I think he should update. It might be that something breaks, but many more problems are solved. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDfcwvtTMYHG2NR9URAudQAJ9kwB94U2+QQQw6xQAuKTNAHV1rDACfWLRO yT1flLq8ldBSfSJgKhbxk5Q= =U5Pg -----END PGP SIGNATURE-----
On Friday 18 November 2005 06:42, Carlos E. R. wrote:
The Thursday 2005-11-17 at 20:30 -0800, Randall R Schulz wrote:
Of course, I still try, sometimes, and inevitably end up dragging out the backup I made before I began. Remember the busted ppp I told you about in 9.1,.2 & .3? All of it caused by updates??
Highly unlikely.
I remember he had problem after some updates, we talked about them here at the time. Some of those problems I had as well: pppd was certainly broken in 9.1, and got solved in 9.3.
Nevertheless, I think he should update. It might be that something breaks, but many more problems are solved.
-- Cheers, Carlos Robinson
Begging your pardon... I don't get it. If anything breaks then the 'value of the update' issue would be moot, would it not? There is no reason to fix what is not broken, and even less reason to fix what was already fixed prior to an update. Perhaps, when I have time to muck around, I'll give it a shot --but only one. If the system breaks in any way then there will be no further updates --no matter the supposed value of said update. -- ...Yogich
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2005-11-18 at 08:59 -0600, Yogich wrote:
Nevertheless, I think he should update. It might be that something breaks, but many more problems are solved.
Begging your pardon... I don't get it. If anything breaks then the 'value of the update' issue would be moot, would it not? There is no reason to fix what is not broken, and even less reason to fix what was already fixed prior to an update.
No. You do not now if anything will break. It might, but normally it shouldn't and doesn't. Just wait some days after a patch apears till people comment on it if something breaks. For example, with 9.3 I have had no problems with updates, using that policy. There is only one standing problem with the present kernel: I just reverted to the previous version, and problem solved. The thing is, you are having some problems, and many problems may have already been corected. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDgNMLtTMYHG2NR9URAup+AJ0byvoVb1PBnjQQFs55AkmTLRPkhACfZYY2 9MgfWiDftDR2SQdHEPvk5lA= =zJD/ -----END PGP SIGNATURE-----
Carlos, On Friday 18 November 2005 04:42, Carlos E. R. wrote:
The Thursday 2005-11-17 at 20:30 -0800, Randall R Schulz wrote:
Of course, I still try, sometimes, and inevitably end up dragging out the backup I made before I began. Remember the busted ppp I told you about in 9.1,.2 & .3? All of it caused by updates??
Highly unlikely.
I remember he had problem after some updates, we talked about them here at the time. Some of those problems I had as well: pppd was certainly broken in 9.1, and got solved in 9.3.
The hypothesis was that the update broke pppd in three separate releases of SuSE Linux. I find that improbable in the extreme.
Nevertheless, I think he should update. It might be that something breaks, but many more problems are solved.
There have been transient problems, owing no doubt to the lack of total omniscience on the part of the SuSE engineers, that may lead to problems following an update (just as there are some in every distribution as it comes out of the box), but they're always fixed soon after they're discovered. On the other hand, if people have problems they don't report, then they should not expect them to be fixed, since at least one person must report something to for it to come to the attention of the pertinent engineers at SuSE or upstream, in the software's project team.
-- Cheers, Carlos Robinson
Randall Schulz
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2005-11-18 at 09:20 -0800, Randall R Schulz wrote:
I remember he had problem after some updates, we talked about them here at the time. Some of those problems I had as well: pppd was certainly broken in 9.1, and got solved in 9.3.
The hypothesis was that the update broke pppd in three separate releases of SuSE Linux. I find that improbable in the extreme.
I can not certify when pppd broke, but I can certify that it was broken in 9.1, and the failure appeared in some other versions, probably because they were using the same version of pppd or they applied the same patch upstream/downstream. You only have to search the archive for my reports on pppd, and nobody was able to help me to mend it. Nor him, his problems were worse than mine. I don't blame the updates, though, except that it seems that the updates propagated the failure in 9.1 to other versions, it seems. Several people reported the same problem. Not every body had it, but several did. Just search the archives.
Nevertheless, I think he should update. It might be that something breaks, but many more problems are solved.
There have been transient problems, owing no doubt to the lack of total omniscience on the part of the SuSE engineers, that may lead to problems following an update (just as there are some in every distribution as it comes out of the box), but they're always fixed soon after they're discovered.
On the other hand, if people have problems they don't report, then they should not expect them to be fixed, since at least one person must report something to for it to come to the attention of the pertinent engineers at SuSE or upstream, in the software's project team.
The pppd failure was reported several times here and to feedback at SuSE. Don't tell me that. :-/ - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDfitVtTMYHG2NR9URAuEUAJwIS5i5W8HVBGX4mulU1UU21I7/cACfSs1z QQwa2Mx14exHV79SCjn2djU= =K02j -----END PGP SIGNATURE-----
On Thursday 17 November 2005 22:30, Randall R Schulz wrote:
Yogich,
On Thursday 17 November 2005 20:13, Yogich wrote:
On Thursday 17 November 2005 17:54, Carlos E. R. wrote:
The Thursday 2005-11-17 at 13:39 -0600, Yogich wrote:
Anyone else having cron problems?? I remember on other time, on either
I suppose you have got all YOU patches? There must have been a few, but I can't say if they apply to your problem.
-- Cheers, Carlos Robinson
I learned the hard way --and over several distros-- that one doesn't apply updates to this box unless one wants the distro to break.
Bah!
Maybe other, inferior distributions cannot maintain the integrity of their software in the face necessary upgrades (for security vulnerabilities or other bug fixes), but that is most certainly not the case with SuSE.
You'd do well to run SuSE Watcher, checking for updates on the default interval, and apply all critical updates that become available.
I've got to say, all the superstition people bring to IT really bugs me.
Of course, I still try, sometimes, and inevitably end up dragging out the backup I made before I began. Remember the busted ppp I told you about in 9.1,.2 & .3? All of it caused by updates??
Highly unlikely.
That's why I tend to yawn when one mentions them. ;-) --
Then you should not expect to get effective help from people who recognize and accept the passage of time and the ongoing improvement of the software packages they use.
...Yogich
Randall Schulz
Unfortunately, I bear witness to the fact that, on at least this box, you are most certainly incorrect. I give you SuSE 9, 9.1, 9.2, 9.3 as prime examples of a 'distro that broke' after updating it. Just a good damned thing that I had a good backup to refer to, or I'd have had lots of work ahead of me to get back to where I started. I only wish that what you say would be correct on this box. There are at least one or two others on this list who did their level best to help me get the problem figured out ...to no avail. -- ...Yogich
Yogich, On Friday 18 November 2005 06:56, Yogich wrote:
...
Unfortunately, I bear witness to the fact that, on at least this box, you are most certainly incorrect. I give you SuSE 9, 9.1, 9.2, 9.3 as prime examples of a 'distro that broke' after updating it. Just a good damned thing that I had a good backup to refer to, or I'd have had lots of work ahead of me to get back to where I started. I only wish that what you say would be correct on this box. There are at least one or two others on this list who did their level best to help me get the problem figured out ...to no avail. --
How can I take that seriously when you seem to think that restoring from backups is the only way to back out a YOU-supplied update? The most likely reason the problem was so hard to solve for you was that you bungled some other aspect of the system's configuration by going around the SuSE-supplied update and configuration procedures and software. I've seen all manner of ham-fisted "solutions" proffered here and people who followed them can well be expected to have problems down the line.
...Yogich
Randall Schulz
On Friday 18 November 2005 11:23, Randall R Schulz wrote:
Yogich,
On Friday 18 November 2005 06:56, Yogich wrote:
...
Unfortunately, I bear witness to the fact that, on at least this box, you are most certainly incorrect. I give you SuSE 9, 9.1, 9.2, 9.3 as prime examples of a 'distro that broke' after updating it. Just a good damned thing that I had a good backup to refer to, or I'd have had lots of work ahead of me to get back to where I started. I only wish that what you say would be correct on this box. There are at least one or two others on this list who did their level best to help me get the problem figured out ...to no avail. --
How can I take that seriously when you seem to think that restoring from backups is the only way to back out a YOU-supplied update?
The most likely reason the problem was so hard to solve for you was that you bungled some other aspect of the system's configuration by going around the SuSE-supplied update and configuration procedures and software. I've seen all manner of ham-fisted "solutions" proffered here and people who followed them can well be expected to have problems down the line.
...Yogich
Randall Schulz
<FWIW> What I was referring to was the fact that, before I even started the update job, I backed up the entirety of the root filesystem in the event something went really wrong. Now, I shall not divulge every name that could bear witness, as well, that these problems happened. Some of them are no longer using SuSE, for one thing, so cannot be contacted for verification. Further, I did report the problem as a bug to SuSE for each of the distros I had problems with, and I do not know what the eventual outcome was, as I ended up doing some testing for another concern which did not involve SuSE ...and consequently I was not on SuSE for several months. I do not claim to know all there is to know about any given disto. All I know is that I have been using various distros over several years' time, between using for my own use & beta testing for others. Some problems are solved. Others become to big a PITB to fool with --especially if the thing that breaks is of no particular consequence ...like the printer, for instance, on one distro I tested for someone else last winter (using his box). Finally, I have *never_ever* gone around the SuSE update process --via apt, or any other means, and my previous notebook --a Toshiba-- didn't gag anyone's updates. This one does. Sorry you don't like it. Neither do I. ;-) </FWIW> Now I'm back, and cron is the one that is not working. No cron job is executed in /etc/cron.daily. I can run them manually with complete success. I just checked in the Runlevel editor & cron shows itself as 'running'. I did note the fact that there is no crond (and /etc/cron.d is empty, as well) so figure there is a connection. -- ...Yogich
On Friday 18 Nov 2005 14:56, Yogich wrote: snip/
Unfortunately, I bear witness to the fact that, on at least this box, you are most certainly incorrect. I give you SuSE 9, 9.1, 9.2, 9.3 as prime examples of a 'distro that broke' after updating it. Just a good damned thing that I had a good backup to refer to, or I'd have had lots of work ahead of me to get back to where I started. I only wish that what you say would be correct on this box. There are at least one or two others on this list who did their level best to help me get the problem figured out ...to no avail. -- ...Yogich
now theres strange says he typing away on a fully updated 9.2 box that aint broke never now 9.3 theres a different bag of worms thats why i did not touch it Oh and one of my other machines running 10.0 also fully updated aint stopped yet even got kde 3.5rc1 on it .. YMMV mine dont... :-p Pete . -- If Bill Gates had gotten LAID at High School do YOU think there would be a Microsoft ? Of course NOT ! You gotta spend a lot of time at your school Locker stuffing underware up your ass to think , I am going to take on the worlds Computer Industry -------:heard on Cyber Radio.:------- AFFA
On Friday 18 November 2005 15:40, Peter Nikolic wrote:
On Friday 18 Nov 2005 14:56, Yogich wrote: snip/
Unfortunately, I bear witness to the fact that, on at least this box, you are most certainly incorrect. I give you SuSE 9, 9.1, 9.2, 9.3 as prime examples of a 'distro that broke' after updating it. Just a good damned thing that I had a good backup to refer to, or I'd have had lots of work ahead of me to get back to where I started. I only wish that what you say would be correct on this box. There are at least one or two others on this list who did their level best to help me get the problem figured out ...to no avail. -- ...Yogich
now theres strange says he typing away on a fully updated 9.2 box that aint broke never now 9.3 theres a different bag of worms thats why i did not touch it Oh and one of my other machines running 10.0 also fully updated aint stopped yet even got kde 3.5rc1 on it ..
YMMV mine dont... :-p
Pete .
-- If Bill Gates had gotten LAID at High School do YOU think there would be a Microsoft ? Of course NOT !
You gotta spend a lot of time at your school Locker stuffing underware up your ass to think , I am going to take on the worlds Computer Industry
-------:heard on Cyber Radio.:-------
AFFA
You lucky devil, you! 8-) -- ...Yogich
participants (5)
-
Carlos E. R. -
Darryl Gregorash -
Peter Nikolic -
Randall R Schulz -
Yogich