Solved: cron - setusercontext failed for root

2008-04-28 Thread Torsten
The system is VERY much stripped down to the absolute necessary files only. Then it's no longer OpenBSD It can be discussed if an OS where I delete certain files cannot be called by its original name anymore. Anyway, I found that cron needs /etc/login.conf though that file is not mentioned

Re: Solved: cron - setusercontext failed for root

2008-04-28 Thread Otto Moerbeek
On Mon, Apr 28, 2008 at 01:26:47PM +0200, Torsten wrote: The system is VERY much stripped down to the absolute necessary files only. Then it's no longer OpenBSD It can be discussed if an OS where I delete certain files cannot be called by its original name anymore. Anyway, I found that

Re: Solved: cron - setusercontext failed for root

2008-04-28 Thread Peter N. M. Hansteen
Torsten [EMAIL PROTECTED] writes: Anyway, I found that cron needs /etc/login.conf though that file is not mentioned in any documentation. That's odd. On my machines 'man login.conf' gives me a rather informative man page. On OpenBSD, to find something that is in fact not at all documented

Re: Solved: cron - setusercontext failed for root

2008-04-28 Thread Stuart Henderson
On 2008/04/28 13:26, Torsten wrote: The system is VERY much stripped down to the absolute necessary files only. Then it's no longer OpenBSD It can be discussed if an OS where I delete certain files cannot be called by its original name anymore. This has been done to death in the

Re: Solved: cron - setusercontext failed for root

2008-04-28 Thread Torsten
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

Re: Solved: cron - setusercontext failed for root

2008-04-28 Thread Otto Moerbeek
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

Re: Solved: cron - setusercontext failed for root

2008-04-28 Thread Torsten
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? Without any irony: I'm sorry if I didn't make things clear enough! The

Re: Solved: cron - setusercontext failed for root

2008-04-28 Thread Paul de Weerd
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

Re: Solved: cron - setusercontext failed for root

2008-04-28 Thread Torsten
Yes, it is *totally* obvious if you actually know what you're doing. Well, I didn't say I know exactly what I'm doing. If everybody always knew exactly what they're doing, this ML would be obsolete, wouldn't it? Thanks a lot for your explanations (no irony! I've learned from it!)!!! That

Re: Solved: cron - setusercontext failed for root

2008-04-28 Thread Ingo Schwarze
Torsten wrote on Mon, Apr 28, 2008 at 04:42:09PM +0200: If everybody always knew exactly what they're doing, this ML would be obsolete, wouldn't it? No. Knowledge does not obsolete communication. Quite to the contrary, knowledge helps communication. Why would you read this ML if not to help