On 09/04/2023 14:54, Michel Verdier wrote:
Le 8 avril 2023 Max Nikulin a écrit :
There is ready to use one: /usr/lib/systemd/user/emacs.service Perhaps there
is no such file in buster.
/usr/lib/systemd/user is for global system running. If you want to change
something in the service you copy i
On Mon 10 Apr 2023 at 17:39:57 (+0200), zithro wrote:
> On 10 Apr 2023 03:23, David Wright wrote:
> > On Sun 09 Apr 2023 at 21:48:22 (+0200), zithro wrote:
> > > > IOW, while I run crontab -e on bookworm, inside my emacs session,
> > > > I want a subshell to run crontab -l, but the latter has to ru
On Mon 10 Apr 2023 at 08:31:16 (+0200), Michel Verdier wrote:
> Le 10 avril 2023 David Wright a écrit :
>
> > In case it's not clear, bullseye and bookworm are Debian distribution
> > codenames, not hostnames. I can't edit my crontab on a newly installed
> > bookworm system while simultaneously li
On 10 Apr 2023 03:23, David Wright wrote:
On Sun 09 Apr 2023 at 21:48:22 (+0200), zithro wrote:
IOW, while I run crontab -e on bookworm, inside my emacs session,
I want a subshell to run crontab -l, but the latter has to run on
bullseye in order to pick up the old crontab. I'm not sure how
I wou
Le 10 avril 2023 David Wright a écrit :
> In case it's not clear, bullseye and bookworm are Debian distribution
> codenames, not hostnames. I can't edit my crontab on a newly installed
> bookworm system while simultaneously listing my old crontab on the old
> bullseye system on the same computer.
On Sun, 9 Apr 2023 David Wright wrote:
On Sun 09 Apr 2023 at 21:48:22 (+0200), zithro wrote:
[Previously David "Between-the-Lines" Wright wrote:]
IOW, while I run crontab -e on bookworm, inside my emacs session,
I want a subshell to run crontab -l, but the latter has to run on
bullseye in order
On Sun 09 Apr 2023 at 21:48:22 (+0200), zithro wrote:
> > IOW, while I run crontab -e on bookworm, inside my emacs session,
> > I want a subshell to run crontab -l, but the latter has to run on
> > bullseye in order to pick up the old crontab. I'm not sure how
> > I would do that.
>
> Try running
IOW, while I run crontab -e on bookworm, inside my emacs session,
I want a subshell to run crontab -l, but the latter has to run on
bullseye in order to pick up the old crontab. I'm not sure how
I would do that.
Try running :
ssh user@bullseye crontab -l
It will locally list the crontab from re
On Thu 06 Apr 2023 at 18:54:31 (-0400), Greg Wooledge wrote:
> On Thu, Apr 06, 2023 at 05:45:08PM -0500, David Wright wrote:
> > Users (including root) write their crontabs anywhere they like,
> > typically in a directory like ~/.cron/.
>
> Is that... normal? I can't say I've ever seen anyone kee
Le 8 avril 2023 Max Nikulin a écrit :
> On 08/04/2023 22:17, Kushal Kumaran wrote:
>>> Have you ever actually *made* a systemd --user unit file? If so, for
>>> what purpose?
>> I have one. It starts emacs server for me when I login.
>
> There is ready to use one: /usr/lib/systemd/user/emacs.serv
Le 8 avril 2023 Greg Wooledge a écrit :
>> systemd user files can be put in ~/.config/systemd/user/ where you can
>> use git directly
>
> Have you ever actually *made* a systemd --user unit file? If so, for
> what purpose?
$ find .config/systemd/
.config/systemd/
.config/systemd/user
.config/sys
On 08/04/2023 22:17, Kushal Kumaran wrote:
Have you ever actually *made* a systemd --user unit file? If so, for
what purpose?
I have one. It starts emacs server for me when I login.
There is ready to use one: /usr/lib/systemd/user/emacs.service Perhaps
there is no such file in buster.
On Sat, Apr 08 2023 at 08:39:14 AM, Greg Wooledge wrote:
> On Sat, Apr 08, 2023 at 11:16:51AM +0200, Michel Verdier wrote:
>> Le 8 avril 2023 Andrew M. A. Cater a écrit :
>>
>> > Likewise for creating systemd unit files - NEVER "just start editing over
>> > the top" always have an example to work
On 08/04/2023 19:39, Greg Wooledge wrote:
Have you ever actually *made* a systemd --user unit file? If so, for
what purpose?
For LXC unprivileged containers that are stopped on logout.
Do you mean it is exceptional case when default user units need
adjustment? /usr/lib/systemd/user director
On Sat, Apr 08, 2023 at 11:16:51AM +0200, Michel Verdier wrote:
> Le 8 avril 2023 Andrew M. A. Cater a écrit :
>
> > Likewise for creating systemd unit files - NEVER "just start editing over
> > the top" always have an example to work from and save it. You can then
> > commit the series to git if
Le 8 avril 2023 Andrew M. A. Cater a écrit :
> Likewise for creating systemd unit files - NEVER "just start editing over
> the top" always have an example to work from and save it. You can then
> commit the series to git if you want to record exact changes.
systemd user files can be put in ~/.con
On Sat, Apr 08, 2023 at 11:45:50AM +1200, Alex King wrote:
> See man crontab.
>
> There are 2 ways of maintaining your crontab:
>
> crontab [ -u user ] file
> ...
> The first form of this command is used to install a new crontab from some
> named file
>
> I.e. you can keep a file in your
See man crontab.
There are 2 ways of maintaining your crontab:
crontab [ -u user ] file
...
The first form of this command is used to install a new crontab from
some named file
I.e. you can keep a file in your home directory (or anywhere,) update it
and install it when changed using "
On 4/7/23, Anssi Saari wrote:
> Greg Wooledge writes:
>
>> On Thu, Apr 06, 2023 at 05:45:08PM -0500, David Wright wrote:
>>> Users (including root) write their crontabs anywhere they like,
>>> typically in a directory like ~/.cron/.
>>
>> Is that... normal? I can't say I've ever seen anyone keep
On 7/04/23 10:54, Greg Wooledge wrote:
On Thu, Apr 06, 2023 at 05:45:08PM -0500, David Wright wrote:
Users (including root) write their crontabs anywhere they like,
typically in a directory like ~/.cron/.
Is that... normal? I can't say I've ever seen anyone keep a private
copy of their cronta
Greg Wooledge writes:
> On Thu, Apr 06, 2023 at 05:45:08PM -0500, David Wright wrote:
>> Users (including root) write their crontabs anywhere they like,
>> typically in a directory like ~/.cron/.
>
> Is that... normal? I can't say I've ever seen anyone keep a private
> copy of their crontab in t
On Thu, Apr 06, 2023 at 06:54:31PM -0400, Greg Wooledge wrote:
> On Thu, Apr 06, 2023 at 05:45:08PM -0500, David Wright wrote:
> > Users (including root) write their crontabs anywhere they like,
> > typically in a directory like ~/.cron/.
>
> Is that... normal? I can't say I've ever seen anyone k
Tom Furie wrote:
> On Fri, Apr 07, 2023 at 08:05:18AM +0800, k...@openmbox.net wrote:
> > Are the time format in /etc/crontab just random? why they are 6:25, 6:47
> > etc?
>
> They aren't *random*, though they are somewhat arbitrary. The daily tasks
> run at 6:25, a time chosen by someone somewhe
On Fri, Apr 07, 2023 at 08:05:18AM +0800, k...@openmbox.net wrote:
> Are the time format in /etc/crontab just random? why they are 6:25, 6:47
> etc?
They aren't *random*, though they are somewhat arbitrary. The daily tasks
run at 6:25, a time chosen by someone somewhere back in the mists of time a
On 2023-04-07 05:20, davidson wrote:
25 6* * * roottest -x /usr/sbin/anacron || ( cd / &&
run-parts --report /etc/cron.daily )
Are the time format in /etc/crontab just random? why they are 6:25, 6:47
etc?
--
Ken Peng
https://kenpeng.pages.dev/
On Thu, Apr 06, 2023 at 05:45:08PM -0500, David Wright wrote:
> Users (including root) write their crontabs anywhere they like,
> typically in a directory like ~/.cron/.
Is that... normal? I can't say I've ever seen anyone keep a private
copy of their crontab in their home directory like that.
M
On Thu 06 Apr 2023 at 12:28:05 (-0700), Fred wrote:
> On 4/6/23 09:44, Pierre Frenkiel wrote:
> >
> > crontab -l
> >
> > On Thu, 6 Apr 2023, Fred wrote:
> > > I also would like to know when cron.daily scripts run. Greg's
> > > command does
On Thu, 6 Apr 2023 Fred wrote:
[trimmed]
I also would like to know when cron.daily scripts run. Greg's command does
not appear to reveal the time for that script. I ran Greg's command and got
the same result.
$ grep -FA7 "Example of job definition" /etc/crontab ; gre
On 4/6/23 09:44, Pierre Frenkiel wrote:
crontab -l
Pierre Frenkiel
On Thu, 6 Apr 2023, Fred wrote:
On 4/6/23 08:33, Andy Smith wrote:
Hello,
On Thu, Apr 06, 2023 at 07:33:26PM +0800, cor...@free.fr wrote:
For scripts put under /etc/cron.daily, which special time will they be
implemented
of month 1-31
> month 1-12 (or names, see below)
> day of week 0-7 (0 or 7 is Sun, or use names)
>
> So the command shown by Greg Wooledge runs at 6:25 am the comand
>
> test -x /usr/sbin/anacron || ( cd / && run-parts --r
On Thu, Apr 06, 2023 at 01:42:33PM -0400, Stefan Monnier wrote:
> > I also would like to know when cron.daily scripts run. Greg's command does
> > not appear to reveal the time for that script. I ran Greg's command and got
> > the same result.
>
> As explain
> I also would like to know when cron.daily scripts run. Greg's command does
> not appear to reveal the time for that script. I ran Greg's command and got
> the same result.
As explained, his command's output does show the actual time, but
I don't think it's
Hi,
Greg Wooledge wrote:
> > > unicorn:~$ grep daily /etc/crontab
> > > 25 6* * * roottest -x /usr/sbin/anacron || ( cd / && run-parts
> > > --report /etc/cron.daily )
Fred wrote:
> > I also would like to know when cron.daily scripts run. Gre
Le 6 avril 2023 Fred a écrit :
> I also would like to know when cron.daily scripts run. Greg's command does
> not appear to reveal the time for that script. I ran Greg's command and got
> the same result.
Greg shows it:
unicorn:~$ grep daily /etc/crontab
25 6* * * r
On Thu, Apr 06, 2023 at 09:02:15AM -0700, Fred wrote:
> I also would like to know when cron.daily scripts run. Greg's command does
> not appear to reveal the time for that script. I ran Greg's command and got
> the same result.
Then you need to read the documentation fo
crontab -l
Pierre Frenkiel
On Thu, 6 Apr 2023, Fred wrote:
On 4/6/23 08:33, Andy Smith wrote:
Hello,
On Thu, Apr 06, 2023 at 07:33:26PM +0800, cor...@free.fr wrote:
For scripts put under /etc/cron.daily, which special time will they be
implemented?
Greg already showed you how to check
On 4/6/23 08:33, Andy Smith wrote:
Hello,
On Thu, Apr 06, 2023 at 07:33:26PM +0800, cor...@free.fr wrote:
For scripts put under /etc/cron.daily, which special time will they be
implemented?
Greg already showed you how to check this on your own systems.
If you need something to run daily but
Hello,
On Thu, Apr 06, 2023 at 07:33:26PM +0800, cor...@free.fr wrote:
> For scripts put under /etc/cron.daily, which special time will they be
> implemented?
Greg already showed you how to check this on your own systems.
If you need something to run daily but at a specific time, co
On Thu, Apr 06, 2023 at 07:33:26PM +0800, cor...@free.fr wrote:
> For scripts put under /etc/cron.daily, which special time will they be
> implemented?
unicorn:~$ grep daily /etc/crontab
25 6* * * roottest -x /usr/sbin/anacron || ( cd / && run-parts
--report /etc/cron.daily )
Hello list,
For scripts put under /etc/cron.daily, which special time will they be
implemented?
I know they will be run daily, but not sure about the special run time.
And, I found some services like apache2, chkrootkit will put the scripts
in this dir automatically. are they for system
On Friday 05 December 2014 23:44:27 Sven Joachim wrote:
> On 2014-12-05 23:24 +0100, Rainer Dorsch wrote:
> > I have one machine here on which cron.daily is not run reliably with
> > anacron.
> >
> > I see in
> >
> > rd@blackbox:~/Managed/LinuxInst$ grep c
On 2014-12-05 23:24 +0100, Rainer Dorsch wrote:
> I have one machine here on which cron.daily is not run reliably with anacron.
>
> I see in
>
> rd@blackbox:~/Managed/LinuxInst$ grep cron.daily /var/log/syslog
> Dec 1 22:55:11 blackbox anacron[14161]: Job `cron.daily&#x
Hello,
I have one machine here on which cron.daily is not run reliably with anacron.
I see in
rd@blackbox:~/Managed/LinuxInst$ grep cron.daily /var/log/syslog
Dec 1 22:55:11 blackbox anacron[14161]: Job `cron.daily' terminated (mailing
output)
rd@blackbox:~/Managed/LinuxInst$
i.e. i
On Wed, Feb 26, 2014 at 06:43:36AM -0500, Tony Baldwin wrote:
> On Wed, Feb 26, 2014 at 06:41:22AM -0500, Tony Baldwin wrote:
> > On Wed, Feb 26, 2014 at 12:09:05PM +0200, Andrei POPESCU wrote:
> > > On Ma, 25 feb 14, 13:53:39, Tazman Deville wrote:
> > > >
> > > > I DO have anacron installed.
> >
er command
17 ** * * rootcd / && run-parts --report /etc/cron.hourly
25 6* * * roottest -x /usr/sbin/anacron || ( cd / && run-parts
--report /etc/cron.daily )
47 6* * 7 roottest -x /usr/sbin/anacron || ( cd / && run-parts
--report /etc/cron.week
2014-02-26 12:43 GMT+01:00 Tony Baldwin :
> On Wed, Feb 26, 2014 at 06:41:22AM -0500, Tony Baldwin wrote:
> > On Wed, Feb 26, 2014 at 12:09:05PM +0200, Andrei POPESCU wrote:
> > > On Ma, 25 feb 14, 13:53:39, Tazman Deville wrote:
> > > >
> > > > I DO have anacron installed.
> > >
> > > Well, purge
On Wed, Feb 26, 2014 at 06:41:22AM -0500, Tony Baldwin wrote:
> On Wed, Feb 26, 2014 at 12:09:05PM +0200, Andrei POPESCU wrote:
> > On Ma, 25 feb 14, 13:53:39, Tazman Deville wrote:
> > >
> > > I DO have anacron installed.
> >
> > Well, purge (not remove) it then, or adjust /etc/anacrontab as nee
On Wed, Feb 26, 2014 at 12:09:05PM +0200, Andrei POPESCU wrote:
> On Ma, 25 feb 14, 13:53:39, Tazman Deville wrote:
> >
> > I DO have anacron installed.
>
> Well, purge (not remove) it then, or adjust /etc/anacrontab as needed ;)
>
> Kind regards,
> Andrei
Thanks, Andrei,
But could you explain
On Ma, 25 feb 14, 13:53:39, Tazman Deville wrote:
>
> I DO have anacron installed.
Well, purge (not remove) it then, or adjust /etc/anacrontab as needed ;)
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alio
>
> # m h dom mon dow user �command
> 17 * � �* * * � root � �cd / && run-parts --report /etc/cron.hourly
> 15 4 � �* * * � root � �test -x /usr/sbin/anacron || ( cd / && run-parts
> --report /etc/cron.daily )
> 07 3 � �* * 7 � root � �test -x /usr/sbin/anacron ||
/cron.hourly
> 15 4* * * roottest -x /usr/sbin/anacron || ( cd / && run-parts
> --report /etc/cron.daily )
> 07 3* * 7 roottest -x /usr/sbin/anacron || ( cd / && run-parts
> --report /etc/cron.weekly )
> 52 11 * * roottest -x /usr/sbin/anacro
On Tue, Feb 25, 2014 at 01:10:38PM +, Darac Marjal wrote:
> On Mon, Feb 24, 2014 at 01:57:02PM +0100, Tazman Deville wrote:
> > I have a little server running here in my office,
> > and logrotate kept running at c. 7am, and using up 100% CPU.
>
> Logrotate *itself* shouldn't use much CPU. But
ed the line in /etc/crontab to run cron.daily scripts
> at 4:15am, instead of 7:whateveritwas am.
> 15 4 * * *
> Also, in cron.daily/logrotate
> I added
> nice -n 15
> I made these changes two days ago,
> and still, yesterday and today, logrotate is running at 7:30ami-ish,
>
n /etc/crontab to run cron.daily scripts
> > at 4:15am, instead of 7:whateveritwas am.
> > 15 4 * * *
> > Also, in cron.daily/logrotate
> > I added
> > nice -n 15
>
> If you do not want this process to take precedence, why did you choose
> such a low niceness to
ing at c. 7am, and using up 100% CPU.
> > > I changed the line in /etc/crontab to run cron.daily scripts
> > > at 4:15am, instead of 7:whateveritwas am.
> > > 15 4 * * *
> > > Also, in cron.daily/logrotate
> > > I added
> > > nice -n 15
> >
On Mon, 2014-02-24 at 13:57 +0100, Tazman Deville wrote:
> I have a little server running here in my office,
> and logrotate kept running at c. 7am, and using up 100% CPU.
> I changed the line in /etc/crontab to run cron.daily scripts
> at 4:15am, instead of 7:whateveritwas am.
> 15
On Lu, 24 feb 14, 15:06:48, Tazman Deville wrote:
> On Mon, Feb 24, 2014 at 01:57:02PM +0100, Tazman Deville wrote:
> > I have a little server running here in my office,
> > and logrotate kept running at c. 7am, and using up 100% CPU.
> > I changed the line in /etc/cron
On Mon, Feb 24, 2014 at 01:57:02PM +0100, Tazman Deville wrote:
> I have a little server running here in my office,
> and logrotate kept running at c. 7am, and using up 100% CPU.
> I changed the line in /etc/crontab to run cron.daily scripts
> at 4:15am, instead of 7:whateveritwa
I have a little server running here in my office,
and logrotate kept running at c. 7am, and using up 100% CPU.
I changed the line in /etc/crontab to run cron.daily scripts
at 4:15am, instead of 7:whateveritwas am.
15 4 * * *
Also, in cron.daily/logrotate
I added
nice -n 15
I made these changes
Harry Putnam wrote:
> Bob Proulx writes:
> > commenting upon. Because while true for non-root for root if it is
> > root there isn't any user test. For the root user it is purely a
>
> Alright... at last. I've been laying for a chance to pedantic right
> back at you...
:-)
> > check to see if
Bob Proulx writes:
> The particular part I was pedantically talking about was your comment
> that said "checks that it is executable", yes, all good, and then you
> go on to say "*and* sees to it that this user has permission". It was
> that last part, the second part of the _and_ that I was ped
Harry Putnam wrote:
> Bob Proulx writes:
> > Harry Putnam wrote:
> >> I'm still not getting the whole picture of what is supposed to happen
> >> on a machine with both anacron and cron installed.
> >
> > And you might be tired of having me respond about it. :-)
>
> Not on your life! I have a cer
ndness for descriptive and very
helpful posts here.
>> I have lines like the one below in /etc/crontab
>>
>> [...] test -x /usr/sbin/anacron || ( cd / && run-parts --report
>> /etc/cron.daily )
>>
>>
-x /usr/sbin/anacron || ( cd / && run-parts --report
> /etc/cron.daily )
>
> Ok, it tests for the presence of /usr/sbin/anacron, checks that it is
> executable and sees to it that this user has permission to run it.
Yes. The "
in my case and I'm kind of guessing it is the general case.
I have lines like the one below in /etc/crontab
[...] test -x /usr/sbin/anacron || ( cd / && run-parts --report
/etc/cron.daily )
Ok, it tests for the presence of /usr/sbin/an
Harry Putnam:
>
> Ok, maybe a bit of a lamer here but:
>
> What is the /etc/cron.daily/apt script supposed to do?
I agree that this is underdocumented. But you can deduce some bits of
that it does by the apt settings it honours. Part of my
/etc/apt/apt.conf.d/local:
APT {
Bob Proulx writes:
Thanks for the in depth explanations and advice. Very helpful.
>> Of course there are other ways, like removing the
>> /etc/cron.daily/logrotate script altogether and running logrotate
>> from roots' crontab.
>
> Under the principle of "
Harry Putnam wrote:
> One final question: I decided to rename the /etc/cron.daily/logrotate
> script to /etc/cron.daily/00logrotate, so that it runs first. Just in
> case what ever caused my problem ... comes up again. At least
> 00logrotate will have the best chance of getting run.
en if you desired to have
it back you could:
apt-get install anacron
And it would all be as it was before. Either way. In or out.
>47 22 * * *root test -x /usr/sbin/anacron ||
> ( cd / && run-parts --report /etc/cron.daily
>
> edited:
>
&
Curt writes:
> On 2013-10-06, Bob Proulx wrote:
>>
>> I think that comment was basically that /etc/cron.daily/apt doesn't
>> have anything to do with log rotation. So you are barking up the
>> wrong tree.
>
> Maybe he thought that given the apt script i
On Mon, Oct 07, 2013 at 12:09:27PM +, Curt wrote:
> On 2013-10-07, Chris Bannister wrote:
> > Remember what Benny Hill said:
> > https://www.youtube.com/watch?v=R6jaKkE0RsI
>
> but not an assumption
>
> a statement that is assumed to be true and from which a
> conclusion can be drawn;
>
On 2013-10-07, Chris Bannister wrote:
>>
>> Maybe he thought that given the apt script is run before the logrotate
>> script in cron.daily (if indeed they're handled in alphabetical order?
>> (apparently, yes, they're run in 'lexical sort order' order
On Mon, Oct 07, 2013 at 07:57:46AM +, Curt wrote:
> On 2013-10-06, Bob Proulx wrote:
> >
> > I think that comment was basically that /etc/cron.daily/apt doesn't
> > have anything to do with log rotation. So you are barking up the
> > wrong tree.
>
&g
On 2013-10-06, Bob Proulx wrote:
>
> I think that comment was basically that /etc/cron.daily/apt doesn't
> have anything to do with log rotation. So you are barking up the
> wrong tree.
Maybe he thought that given the apt script is run before the logrotate
script in cron
On Sun, 06 Oct 2013 13:19:35 -0400
Harry Putnam wrote:
> Is 25.5 minutes normal for that script?
The script has a sleep for up to 30 minutes, so everybody's script does not hit
the mirrors at the same time.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "
led. You do. So it is
on the cron side of things.
> >> investigating and ran up on /etc/cron.daily/apt
> >
> > Are we on the same page here?
>
> Not really sure what you mean there.
I think that comment was basically that /etc/cron.daily/apt doesn't
have anyt
| Version table:
| *** 3.8.6-1 0
| 500 http://ftp.us.debian.org/debian/ jessie/main i386 Packages
| 100 /var/lib/dpkg/status
`
>> investigating and ran up on /etc/cron.daily/apt
>
> Are we on the same page here?
Not really sure what you mean there.
I guess it w
On Sat, Oct 05, 2013 at 10:39:38AM -0400, Harry Putnam wrote:
> Logrotation is not happening for some reason, so stumbling around
What is output of:
apt-cache policy logrotate
> investigating and ran up on /etc/cron.daily/apt
Are we on the same page here?
> What is the /etc/cron.
Logrotation is not happening for some reason, so stumbling around
investigating and ran up on /etc/cron.daily/apt
Ok, maybe a bit of a lamer here but:
What is the /etc/cron.daily/apt script supposed to do?
Looking thru the script, I couldn't make heads or tails of it.
--
To UNSUBS
On Wed, 25 Jul 2012 15:06:11 -0600, Bob Proulx wrote:
>Jeff Grossman wrote:
>> I just did a "grep source *" from the /etc/cron.daily directory to
>> figure out what file is causing me the problems. But, it came back
>> empty. How would I figure out where that sou
urrent directory. Dash
>>DOESN'T do this.
>>
>>That is, assuming somefile.sh is in the current directory, "source
>>somefile.sh" will work in bash, but not dash. To fix this bashism, use
>>"source ./somefile.sh".
>
> I just did a "grep s
Jeff Grossman wrote:
> I just did a "grep source *" from the /etc/cron.daily directory to
> figure out what file is causing me the problems. But, it came back
> empty. How would I figure out where that source file is to fix it?
> The e-mail is my daily cron.daily cron job
rection to figure out what file in cron.daily is giving me
>> this error?
>>
>>
>> -su: source: not found
>
>I imagine that your system shell has been changed to dash (run "ls -l /bin/sh"
>to check). Dash is somewhat stricter in its implementation of POS
On Wed, Jul 25, 2012 at 06:13:31AM -0700, Jeff Grossman wrote:
> Since I have upgraded to Squeeze, I get and e-mail with the following
> line in it every morning. Would somebody be able to point me in the
> right direction to figure out what file in cron.daily is giving me
>
Since I have upgraded to Squeeze, I get and e-mail with the following
line in it every morning. Would somebody be able to point me in the
right direction to figure out what file in cron.daily is giving me
this error?
-su: source: not found
Thanks,
Jeff
--
To UNSUBSCRIBE, email to debian
- so why not put them all in the same script? Then you can do
clever things like checking if the previous one actually succeeded. And
you don't need to care if the implementation of cron.daily changes, and
it's simpler to call it from cron.d if you decide to run it at a
specific time, or w
On Thu, 05 Jan 2012 16:37:45 +, T o n g wrote:
> On Thu, 05 Jan 2012 15:32:37 +, Camaleón wrote:
>
>> You can add a #comment inside the scripts themselves remembering how
>> hard is to get them sorted and run at the desired order ;-)
>
> ROTFL. Camaleón, you just won't admit that you eve
On Thu, 05 Jan 2012 15:32:37 +, Camaleón wrote:
> You can add a #comment inside the scripts themselves remembering how
> hard is to get them sorted and run at the desired order ;-)
ROTFL. Camaleón, you just won't admit that you ever neglect something,
will you. :-)
--
Tong (remove undersco
On Thu, 05 Jan 2012 15:31:50 +0100, Vincent Lefevre wrote:
> On 2012-01-04 16:59:27 +, Camaleón wrote:
>> On Wed, 04 Jan 2012 01:18:35 +0100, Vincent Lefevre wrote:
>> > The point is that the behavior can depend on the locales. To avoid
>> > that, users should use only lowercase letters for th
Bonjour,
nous developpons une carte arm avec un omap
souhaiterions rencontrer dans le sud de la france pour porter debian sur
nos machines
vous pouvez nous contcater sur cet email
br
wb
+33495053845
On Wed, 04 Jan 2012 19:03:22 +, T o n g wrote:
> On Wed, 04 Jan 2012 16:59:27 +, Camaleón wrote:
>
>> Yup, but this can be found by simply "trial and error" tests.
>
> trial and error can sure yield some conclusion, but whether the
> conclusion is good really depend on the trials.
If yo
On 2012-01-04 16:59:27 +, Camaleón wrote:
> On Wed, 04 Jan 2012 01:18:35 +0100, Vincent Lefevre wrote:
> > The point is that the behavior can depend on the locales. To avoid that,
> > users should use only lowercase letters for the name of these scripts
> > and be careful with the non-alphabeti
ood really depend on the trials.
>
> For Vincent's case specifically, I believe no matter how many trials I
> did, I would never realize it.
I wouldn't have thought the order of jobs in cron.daily ought to matter,
but if it does, why not just give them names like "10FirstJob&quo
On Wed, 04 Jan 2012 16:59:27 +, Camaleón wrote:
> Yup, but this can be found by simply "trial and error" tests.
trial and error can sure yield some conclusion, but whether the
conclusion is good really depend on the trials.
For Vincent's case specifically, I believe no matter how many tria
On Wed, 04 Jan 2012 01:18:35 +0100, Vincent Lefevre wrote:
> On 2012-01-03 15:30:16 +, Camaleón wrote:
>> Nah... the basics for making the script to run before/after another one
>> placed there are already told. The rest of the problems (if any) are
>> rather "cosmetics" ;-P
>
> The point is
On 2012-01-03 15:30:16 +, Camaleón wrote:
> Nah... the basics for making the script to run before/after another one
> placed there are already told. The rest of the problems (if any) are
> rather "cosmetics" ;-P
The point is that the behavior can depend on the locales. To avoid
that, users s
0, T o n g wrote:
>> >>
>> >> > How is the execution order of cron.daily jobs determined?
>> >>
>> >> I think it is alphabetically.
>> >
>> > No need to guess:
>> >
>> > $ grep cron.daily /etc/crontab
>>
Vincent Lefevre wrote:
> The problem is that the sort order depends on the locales, so that
> the question becomes: what locale is taken into account for
> cron.daily?
By default you will get the system locale setting that is configured
in /etc/default/locale and configured by the
On 2012-01-03 03:13:43 +, T o n g wrote:
> On Mon, 02 Jan 2012 17:45:45 +, Tony van der Hoff wrote:
>
> >> How is the execution order of cron.daily jobs determined?
> >>. . .
> >
> > the same order as ls -s, ie. alphanumerically.
>
> I thought
On Mon, 02 Jan 2012 17:45:45 +, Tony van der Hoff wrote:
>> How is the execution order of cron.daily jobs determined?
>>. . .
>
> the same order as ls -s, ie. alphanumerically.
I thought so. Thanks everyone.
--
Tong (remove underscore(s) to reply)
http://xpt.source
1 - 100 of 324 matches
Mail list logo
