On Mon, Apr 28, 2008 at 03:17:34PM +0200, Torsten wrote:
>> Are you serious? You break things by removing an essential, documented
>> file and then complain?
>
> It's obvious that I must be dumb. I wasn't smart enough to find out that
> running a program by schedule (which cron does) _must_ have something to do
> with the _login_ process, which login.conf is obviously related to!!! As if
> that wasn't obvious!!! ;-)
>
> Stupid as I am I thought that documentation of cron would point to the
> files that cron relies upon. Or at least, if it finds a file missing, it
> would tell me which one it is. Stupid me! ;-)
Lemme tell you there are more files on which cron relies that are not
in the cron man pages. The function call that was in error
(setusercontext()) clearly cross references login.conf.
>
>
> > Please stop wasting our time.
>
> And after not finding a solution by reading documentation and trying all
> sorts of debugging options, I was so stupid to ask this ML if someone has
> an idea which files cron would need. I'm so sorry to have wasted your
> precious time! Again: stupid me! I apologize.
>
> Anyway, I'm glad Stuart Henson was kind enough to point an obvious idiot
> like me also to setusercontext (3), which finally led me to find cron is
> missing login.conf. @Stu: Thx alot!
If you start breaking stuff by removing files without the knowledge
how things work, you should expect harsh treatment from this list.
What's next, sombody complaining he cannot login because he removed
the passwd file?
-Otto
