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
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
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
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
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
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
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
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:
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
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
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
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
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
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
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
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
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
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
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.
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 not appear to reveal the time for that script. I
> > >
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 ; grep daily /etc/crontab
#
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?
On Thu, 2023-04-06 at 19:05 +0200, Thomas Schmitt wrote:
> Hi,
>
>
> Pierre Frenkiel wrote:
> > crontab -l
>
> Plus:
> man 5 crontab
> which has in its section "EXAMPLE CRON FILE"
>
> # run five minutes after midnight, every day
> 5 0 * * * $HOME/bin/daily.job >>
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 explained, his command's output does show
> 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 the whole story: AFAIK the actual
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. Greg's command does
> > not appear to reveal
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* * * roottest -x
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 for cron. I'd suggest
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, consider
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
40 matches
Mail list logo
