[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] RaQ4i - Crontab Died After Kernel Update --FIXED
- Subject: Re: [cobalt-users] RaQ4i - Crontab Died After Kernel Update --FIXED
- From: David Thurman <dthurman@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon Sep 24 04:06:05 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
on 9-24-01 12:44 PM, Barbara - at thebizworkers@xxxxxxxxx was reported to
have made a statement that said this:
> Ya know... I really should take some of the things I
> read on these Cobalt lists with a grain of salt. I
> just figured out what killed crontab, even though the
> daemon was still running.
>
> A week or two ago, I came across a post on the Cobalt
> security list regarding a suggestion on how to "stop
> naughty CGI 'exploits'" (as it was stated -
> http://list.cobalt.com/pipermail/cobalt-security/2001-September/003445.html).
> It was obviously of good intentions as the poster
> suggested to chmod 0700 /usr/sbin/inetd, which should
> stop anyone but root from running inetd. Thus as
> stated, would prevent the easiest way of getting root
> in the known universe (via inetd).
>
> So I thought what a good idea, I'll try that on my
> system. Luckily, I was first smart enough to check to
> make sure inetd wasn't set with the SUID bit on, as I
> knew that would cause a major nightmare and would
> certainly break something if it was on. It wasn't,
> just plain old 755 permissions, so I fiugred it was
> safe to change permissions to 700 as I could always
> change it back if it did break something.
>
> Well, it seemed to work until the latest kernel was
> installed, then my crontab went tits up and stopped
> working all together. Then I thought maybe that was
> the problem, so I reset permissions back to 755 and
> rebooted the machine and everything is back to normal.
> Crontab is happy and working again just as it should
> be.
>
> Just goes to show you, we all might want to think
> twice before going under the hood just on some
> recommendation. Who knows what might break.
>
> Take Care
> Barbara
>
Our crontab stopped working and we didn't touch a thing. Except to put the
new patch in for a Raq3. I looked at our perms and they say 755 as root in
our cron.daily
Any thoughts??
>
--
Thank you,
David E Thurman
Web Presence Group
309.676.5688
dthurman@xxxxxxxxxxxxxxxxxxxx
http://www.webpresencegroup.net