Quantcast

Odd cron errors

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Odd cron errors

Jamie-68
I'm running cron in a jail, and I see these errors filling up crons
logfile

It *appears* to be coming from atrun, wanting to set up priority
from /etc/login.conf

if (setusercontext(NULL, pentry, uid, LOGIN_SETALL &
                ~(LOGIN_SETPRIORITY | LOGIN_SETPATH | LOGIN_SETENV)) !=
                                0)
                                            exit(EXIT_FAILURE); /* setusercontext()
                                                        logged the error */

I actually very much do NOT want atrun to be tinkering with the
priority (as I'd like to have it run in the idle task eventually)

Is there a way, short of recompiling, that I can convince atrun
not to do this?

Jamie


18:10:00 web cron[]: setpriority 'root' (daemon): Permission denied
18:11:00 web /usr/sbin/cron[]: (operator) CMD (/usr/libexec/save-entropy)
18:11:00 web cron[]: setpriority 'operator' (daemon): Permission denied
18:15:00 web /usr/sbin/cron[]: (root) CMD (/usr/libexec/atrun)
18:15:00 web cron[]: setpriority 'root' (daemon): Permission denied

--
http://www.geniegate.com                    Custom web programming
Perl * Java * UNIX                        User Management Solutions
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-chat
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Odd cron errors

Dag-Erling Smørgrav
Jamie <[hidden email]> writes:
> I actually very much do NOT want atrun to be tinkering with the
> priority (as I'd like to have it run in the idle task eventually)
>
> Is there a way, short of recompiling, that I can convince atrun
> not to do this?

How about disabling atrun?

DES
--
Dag-Erling Smørgrav - [hidden email]
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-chat
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Odd cron errors

Jamie-68
On Wed, Mar 16, 2011 at 04:03:25PM +0100, Dag-Erling Sm??rgrav wrote:
> Jamie <[hidden email]> writes:
> > I actually very much do NOT want atrun to be tinkering with the
> > priority (as I'd like to have it run in the idle task eventually)
> >
> > Is there a way, short of recompiling, that I can convince atrun
> > not to do this?
>
> How about disabling atrun?

I use at/batch *constantly* (especially batch)

The machine I'm replacing was setup to run cron under idprio 31 (outside
the jail) specifically so that jobs ran during the idle task.

Disabling is a no-go.

Jamie
--
http://www.geniegate.com                    Custom web programming
Perl * Java * UNIX                        User Management Solutions
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-chat
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Odd cron errors

Dag-Erling Smørgrav
Jamie <[hidden email]> writes:
> Dag-Erling Smørgrav <[hidden email]> writes:
> > How about disabling atrun?
> I use at/batch *constantly* (especially batch)

Wow.  I don't know of anybody else who does...  I always thought of it
as a relic.

DES
--
Dag-Erling Smørgrav - [hidden email]
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-chat
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Odd cron errors

soralx

> Jamie <[hidden email]> writes:
> > Dag-Erling Smørgrav <[hidden email]> writes:
> > > How about disabling atrun?
> > I use at/batch *constantly* (especially batch)
>
> Wow.  I don't know of anybody else who does...  I always thought of it
> as a relic.

I use at often. On one of workstations, job numbers are in 800's already.

> DES


--
[SorAlx]  ridin' VN2000 Classic LT
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-chat
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Odd cron errors

Oliver Fromme
In reply to this post by Jamie-68
[hidden email] wrote:
 > > Jamie <[hidden email]> writes:
 > > > Dag-Erling Smørgrav <[hidden email]> writes:
 > > > > How about disabling atrun?
 > > > I use at/batch *constantly* (especially batch)
 > >
 > > Wow.  I don't know of anybody else who does...  I always thought of it
 > > as a relic.
 >
 > I use at often. On one of workstations, job numbers are in 800's already.

I use at sometimes as a simple reminder service, like this:

$  at 16:00 monday <<<'echo Remember to buy flowers'

("<<<" is zsh + bash syntax for feeding stuff to stdin;
our /bin/sh doesn't recognize it, unfortunately.)

Best regards
   Oliver

--
Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M.
Handelsregister: Registergericht Muenchen, HRA 74606,  Geschäftsfuehrung:
secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün-
chen, HRB 125758,  Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart

FreeBSD-Dienstleistungen, -Produkte und mehr:  http://www.secnetix.de/bsd

"C++ is to C as Lung Cancer is to Lung."
        -- Thomas Funke
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-chat
To unsubscribe, send any mail to "[hidden email]"
Loading...