On 29/02/2024 11:32, David Wright wrote:
On Wed 28 Feb 2024 at 22:32:57 (+0700), Max Nikulin wrote:
On 28/02/2024 10:35, David Wright wrote:
In which case, I'd write the remaining cron line as:
@reboot sleep 99 && echo 13b1 0bdc > /sys/bus/usb/drivers/brcmfmac/new_id
I am in doubts if
On Wed 28 Feb 2024 at 22:32:57 (+0700), Max Nikulin wrote:
> On 28/02/2024 10:35, David Wright wrote:
> > In which case, I'd write the remaining cron line as:
> >
> >@reboot sleep 99 && echo 13b1 0bdc > /sys/bus/usb/drivers/brcmfmac/new_id
>
> I am in doubts if it is a task for cron.
On 29/02/2024 00:00, Kamil Jońca wrote:
How precisely linger works? (what it starts? What not etc)
I read about lingering some time ago, and I have had impression
(wrong?) that it may conflict with my normal session.
Multiple sessions may be started for a user: DM, ssh, VT logins. I am
Andy Smith writes:
> Hi,
>
> On Wed, Feb 28, 2024 at 04:47:59PM +0100, Kamil Jońca wrote:
>> Andy Smith writes:
>> > Once you enable lingering for a user, that user's timers will
>> > trigger all the time.
>>
>> IIRC lingered user cannot be "normal" with session and so on. Am I
>> wrong?
>
>
Hi,
On Wed, Feb 28, 2024 at 04:47:59PM +0100, Kamil Jońca wrote:
> Andy Smith writes:
> > Once you enable lingering for a user, that user's timers will
> > trigger all the time.
>
> IIRC lingered user cannot be "normal" with session and so on. Am I
> wrong?
How do you mean? On several
Andy Smith writes:
> Hi,
>
> On Wed, Feb 28, 2024 at 05:49:58AM +0100, Kamil Jońca wrote:
>> With cron, regular user can set up his/her jobs wihtout using admin
>> credentials, and these jobs will be triggered regardless of being logged
>> in. Is it possible with systemd timers?
>
> Once you
Max Nikulin (12024-02-28):
> I am in doubts if it is a task for cron. Wouldn't udev rules be better?
Or even the good old simple way that still works:
install modulename command...
This command instructs modprobe to run your command instead of
inserting the module in
On 28/02/2024 10:35, David Wright wrote:
In which case, I'd write the remaining cron line as:
@reboot sleep 99 && echo 13b1 0bdc > /sys/bus/usb/drivers/brcmfmac/new_id
I am in doubts if it is a task for cron. Wouldn't udev rules be better?
Hi,
On Wed, Feb 28, 2024 at 05:49:58AM +0100, Kamil Jońca wrote:
> With cron, regular user can set up his/her jobs wihtout using admin
> credentials, and these jobs will be triggered regardless of being logged
> in. Is it possible with systemd timers?
Once you enable lingering for a user, that
Hello,
On Tue, Feb 27, 2024 at 02:58:13PM -0500, Greg Wooledge wrote:
> I don't foresee real cron going away any time soon.
If you today install bookworm base system and select no packages,
the only reason why you get cron is because logrotate depends upon
it. If you do not need logrotate then
Gremlin writes:
[...]
>
> https://wiki.archlinux.org/title/Systemd-networkd
> https://wiki.archlinux.org/title/Wireless_bonding
>
> I am using systemd-networkd and systemd-resolved and have removed
> Networkmanager, ifupdown and isc-dhcp. Also avahi, modemmanager,
> openssh-sftp-server
w_id
where you can choose a better estimate than 99.
> > Anyway, that got me down the rabbit hole to try to find where the crontab
> > file is.
>
> Per-user crontabs are in /var/spool/cron/crontabs, or at least are in
> Bookworm (and this has been the case for what feels like forev
On Tue, Feb 27, 2024 at 10:12:11PM -0500, The Wanderer wrote:
> On 2024-02-27 at 14:09, Gary Dale wrote:
> > as does find / -name crontab
>
> Invoked how? In particular, as which user?
>
> Assuming that the crontab files are actually named literally 'crontab'
> with no e
On 2024-02-27 at 14:09, Gary Dale wrote:
> On 2024-02-27 10:26, The Wanderer wrote:
>
>> On 2024-02-27 at 10:15, Gary Dale wrote:
>>
>>> Anyway, that got me down the rabbit hole to try to find where the
>>> crontab file is.
>>>
>>>
On 2/27/24 14:58, Greg Wooledge wrote:
On Tue, Feb 27, 2024 at 12:52:33PM -0700, Charles Curley wrote:
On Tue, 27 Feb 2024 14:13:49 -0500
Jeffrey Walton wrote:
The debian wiki suggests that the handling of cron/anacron is
evolving.
That sounds like a euphemism for "being killed off" by
On 2/27/24 14:33, Gary Dale wrote:
On 2024-02-27 14:13, Jeffrey Walton wrote:
On Tue, Feb 27, 2024 at 2:12 PM Gary Dale wrote:
On 2024-02-27 10:25, Kushal Kumaran wrote:
On Tue, Feb 27 2024 at 10:15:59 AM, Gary Dale
wrote:
[...]
Can anyone explain how Trixie is handling crontabs now?
This
On Tue, Feb 27, 2024 at 12:52:33PM -0700, Charles Curley wrote:
> On Tue, 27 Feb 2024 14:13:49 -0500
> Jeffrey Walton wrote:
>
> > > The debian wiki suggests that the handling of cron/anacron is
> > > evolving.
> >
> > That sounds like a euphemism for "being killed off" by Systemd and
> > its
On Tue, 27 Feb 2024 14:13:49 -0500
Jeffrey Walton wrote:
> > The debian wiki suggests that the handling of cron/anacron is
> > evolving.
>
> That sounds like a euphemism for "being killed off" by Systemd and
> its timers.
These days cron and anacron are run as services/timers by systemd.
On 2024-02-27 14:13, Jeffrey Walton wrote:
On Tue, Feb 27, 2024 at 2:12 PM Gary Dale wrote:
On 2024-02-27 10:25, Kushal Kumaran wrote:
On Tue, Feb 27 2024 at 10:15:59 AM, Gary Dale wrote:
[...]
Can anyone explain how Trixie is handling crontabs now?
This behavior has existed forever. I'm
On Tue, Feb 27, 2024 at 2:12 PM Gary Dale wrote:
>
> On 2024-02-27 10:25, Kushal Kumaran wrote:
> > On Tue, Feb 27 2024 at 10:15:59 AM, Gary Dale
> > wrote:
> >> [...]
> >> Can anyone explain how Trixie is handling crontabs now?
> > This behavior has existed forever. I'm on bookworm, though,
ers/brcmfmac/new_id
However when I add those lines to the root's crontab using # crontab -e as
@reboot /usr/sbin/modprobe brcmfmac
@reboot echo 13b1 0bdc > /sys/bus/usb/drivers/brcmfmac/new_id
the second line fails. I get an e-mail stating "/bin/sh: 1: cannot create
/sys/bus/usb/drivers/brcm
ers/brcmfmac/new_id
However when I add those lines to the root's crontab using # crontab -e as
@reboot /usr/sbin/modprobe brcmfmac
@reboot echo 13b1 0bdc > /sys/bus/usb/drivers/brcmfmac/new_id
the second line fails. I get an e-mail stating "/bin/sh: 1: cannot
create /sys/bus/usb/drivers/brcm
On 2024-02-27 10:26, The Wanderer wrote:
On 2024-02-27 at 10:15, Gary Dale wrote:
Anyway, that got me down the rabbit hole to try to find where the
crontab file is.
ls -l /root/cron*
ls: cannot access '/root/cron*': No such file or directory
also
# whereis crontab
crontab: /usr/bin
On 27 Feb 2024 10:15 -0500, from g...@extremeground.com (Gary Dale):
> However when I add those lines to the root's crontab using # crontab -e as
>
> @reboot /usr/sbin/modprobe brcmfmac
> @reboot echo 13b1 0bdc > /sys/bus/usb/drivers/brcmfmac/new_id
>
> the second line f
gt;
> However when I add those lines to the root's crontab using # crontab -e as
>
> @reboot /usr/sbin/modprobe brcmfmac
> @reboot echo 13b1 0bdc > /sys/bus/usb/drivers/brcmfmac/new_id
>
> the second line fails. I get an e-mail stating "/bin/sh: 1: cannot create
&g
On 2024-02-27 at 10:15, Gary Dale wrote:
> Anyway, that got me down the rabbit hole to try to find where the
> crontab file is.
>
> ls -l /root/cron*
> ls: cannot access '/root/cron*': No such file or directory
>
> also
>
> # whereis crontab
> crontab: /usr
> However when I add those lines to the root's crontab using # crontab -e as
>
> @reboot /usr/sbin/modprobe brcmfmac
> @reboot echo 13b1 0bdc > /sys/bus/usb/drivers/brcmfmac/new_id
>
> the second line fails. I get an e-mail stating "/bin/sh: 1: cannot
> create /sys/bus/
I'm running Debian/Trixie on an AMD64 system. I have an old wifi adapter
that Linux has problems with that works once I run:
/usr/sbin/modprobe brcmfmac
echo 13b1 0bdc > /sys/bus/usb/drivers/brcmfmac/new_id
However when I add those lines to the root's crontab using # crontab -e as
@reb
ruby (3.x). For example, different streaming
> libraries for ruby require different versions.
>
> For instance, I developed a ruby client for Kafka streaming, and
> deployed it in crontab, and this script must use ruby 3.x version.
>
> 0 * * * * ruby kafka-consumer.rb
>
&g
debian-u...@howorth.org.uk (12023-03-17):
> Please don't send me an individual copy of emails; I am subscribed.
Nobody can remember who is subscribed and who is not: do not write this
in your mail, write it in the headers, just like I did.
--
Nicolas George
> > installed in the system by rbenv.
> > > >
> > > > Since I often change default ruby in interactive shell, this may
> > > > break the ruby for sysadmin job in crontab. What’s the solution
> > > > for this?
> > >
> > > Everywher
d a ruby client for Kafka streaming, and deployed it
> in crontab, and this script must use ruby 3.x version.
>
> 0 * * * * ruby kafka-consumer.rb
How is cron going to know which ruby to use? Cron uses a very minimalist
PATH. From crontab(5):
Several environment variables
developed a ruby client for Kafka streaming, and
deployed it in crontab, and this script must use ruby 3.x version.
0 * * * * ruby kafka-consumer.rb
But one day I changed the default version in my personal path to ruby
1.x via rbenv, the crontab above should not work. This is a risk, is it?
regards
Yong
> > >
> > > > Since I often change default ruby in interactive shell, this may
> > > > break the ruby for sysadmin job in crontab. What’s the solution for
> > > > this?
> > >
> > > Everywhere it matters, set an explicit PATH at the be
eractive shell, this may
> > > break the ruby for sysadmin job in crontab. What’s the solution for
> > > this?
> >
> > Everywhere it matters, set an explicit PATH at the beginning.
> >
> > There is no other solution.
>
> Err, I know nothing about the subject
Dan Ritter wrote:
> p...@ymail.ne.jp wrote:
> > For dev stuff, for example, I have many versions of ruby installed
> > in the system by rbenv.
> >
> > Since I often change default ruby in interactive shell, this may
> > break the ruby for sysadmin jo
2023, Dan Ritter wrote:
> p...@ymail.ne.jp wrote:
> > For dev stuff, for example, I have many versions of ruby installed in the
> > system by rbenv.
> >
> > Since I often change default ruby in interactive shell, this may break the
> > ruby for s
p...@ymail.ne.jp wrote:
> For dev stuff, for example, I have many versions of ruby installed in the
> system by rbenv.
>
> Since I often change default ruby in interactive shell, this may break the
> ruby for sysadmin job in crontab. What’s the solution for this?
Everywhere
For dev stuff, for example, I have many versions of ruby installed in the
system by rbenv.
Since I often change default ruby in interactive shell, this may break the ruby
for sysadmin job in crontab. What’s the solution for this?
Greg Wooledge (12023-03-16):
> So they installed
> parallel toolsets (commands including ps, echo, and so on) in two
> different directories.
Four: there is also /usr/xpg4/bin and /usr/xpg6/bin.
Regards,
--
Nicolas George
On Thu, Mar 16, 2023 at 01:57:26PM +0100, Christoph Brinkhaus wrote:
> I think you are right. The only remaining argument for specifying the
> complete path I have read about is as below.
> There might be the situation with different binaries but similar
> names. For example /usr/bin/nc is
Am Thu, Mar 16, 2023 at 07:27:22AM -0400 schrieb Greg Wooledge:
> On Thu, Mar 16, 2023 at 12:24:10PM +0100, Christoph Brinkhaus wrote:
> > The environments of login shells and crontab can be different. This
> > includes the path where to seek executables. Therefore it is go
On Thu, Mar 16, 2023 at 12:24:10PM +0100, Christoph Brinkhaus wrote:
> The environments of login shells and crontab can be different. This
> includes the path where to seek executables. Therefore it is good
> practice not to write just the name of the executable as nc but the
> name w
Am Thu, Mar 16, 2023 at 08:55:54AM +0800 schrieb cor...@free.fr:
> Greetings,
>
> My script for monitoring Node.js app as follows. I put it in crontab for
> auto-check and restart if failure.
>
> #!/bin/bash
>
> # scan the port
> nc -z 127.0.0.1 3000
>
> if
Greg Wooledge (12023-03-16):
> That assumes you want to detach the process from its session in the
> first place. It's NOT what you should do when running a managed
> service, though.
>
> With a managed service, you don't want ANY of the old legacy "I want
> to run a daemon from an interactive
On Thu, Mar 16, 2023 at 08:53:55AM +0100, Nicolas George wrote:
> cor...@free.fr (12023-03-16):
> > nohup serve -s /home/myUsername/workspace/xxx-frontend/build &
>
> What Greg said. Plus:
>
> Never use nohup. nohup should never have been invented, it is based on a
> complete lack of
cor...@free.fr (12023-03-16):
> nohup serve -s /home/myUsername/workspace/xxx-frontend/build &
What Greg said. Plus:
Never use nohup. nohup should never have been invented, it is based on a
complete lack of understanding of how sessions and control terminal
work.
Instead:
- use setsid to
updated: Thanks for all your helps, especially @Greg and @Yong
Now this systemd service has been enabled and just works.
I put a file on /etc/systemd/system/xxx.service whose content as,
[Unit]
Description=xxx Front
After=network.target
[Service]
Type=simple
Restart=always
RestartSec=5
On 16/3/23 12:09, p...@ymail.ne.jp wrote:
Just for fun, I asked this question on ChatGPT, who gives the answers
as follows.
Q: Please help generate a systemd configuration for Debian linux
A: Sure, here's an example of a systemd configuration file for a
Debian Linux service:
Be very
Just for fun, I asked this question on ChatGPT, who gives the answers as
follows.
Q: Please help generate a systemd configuration for Debian linux
A: Sure, here's an example of a systemd configuration file for a Debian
Linux service:
```
[Unit]
Description=My Service
After=network.target
cor...@free.fr wrote:
where will I setup this script for systemd job? any reference?
You might look at this article as well.
https://linuxhandbook.com/create-systemd-services/
Yong
gt;
> > #!/bin/sh
> > PATH=/whatver/you/need
> > while true; do
> > serve -s /path/to/your/service
> > sleep 5
> > done
> >
> > Then arrange for this script to be executed at boot time, and that's it.
> > No background stuff, no polling fr
On 16/03/2023 09:32, Greg Wooledge wrote:
On Wed, Mar 15, 2023 at 08:00:20PM -0500, Nicholas Geovanis wrote:
On Wed, Mar 15, 2023, 7:56 PM wrote:
> My script for monitoring Node.js app as follows. I put it in crontab for
> auto-check and restart if failure.
There's so much
On Wed, Mar 15, 2023 at 08:00:20PM -0500, Nicholas Geovanis wrote:
> On Wed, Mar 15, 2023, 7:56 PM wrote:
> > My script for monitoring Node.js app as follows. I put it in crontab for
> > auto-check and restart if failure.
There's so much wrong with that.
If you want to m
On Wed, Mar 15, 2023, 7:56 PM wrote:
> Greetings,
>
> My script for monitoring Node.js app as follows. I put it in crontab for
> auto-check and restart if failure.
>
> #!/bin/bash
>
> # scan the port
> nc -z 127.0.0.1 3000
>
> if [ $? -eq 0 ];then
>exit
&
Greetings,
My script for monitoring Node.js app as follows. I put it in crontab for
auto-check and restart if failure.
#!/bin/bash
# scan the port
nc -z 127.0.0.1 3000
if [ $? -eq 0 ];then
exit
else
killall node
sleep 1
nohup serve -s /home/myUsername/workspace/xxx-frontend/build
l'exclusió de cron, i
l'anacron hauria de tenir prevista la interpretació de /etc/crontab
--
Narcis Garcia
__
I'm using this dedicated address because personal addresses aren't
masked enough at this mail public archive. Public archive administrator
should fix this against automated
importa.
Havent desinstal·lat anacron, només amb això el programet ja s'executa a
l'hora programada al /etc/crontab
He trobat que l'anacron s'instal·la per dependència dels paquets:
task-desktop
task-laptop
Així que als servidors (CLI) no se'ls instal·la anacron de forma
imprevista mentre
Hola, Narcis:
> Els paquets cron i anacron haurien de ser incompatibles, perquè
> això és una xapussa important davant quan fas cas de la teoria
> bàsica i fas servir la magnífica estructura de directoris
> /etc/cron.*
Doncs jo trobo que és una combinació força enginyosa i que evita
configurar
l 11/2/23 a les 17:24, Narcis Garcia ha escrit:
>> Salut a tothom.
>>
>> Tinc un ordinador sempre engegat que necessito que es
reiniciï cada
>> dia ben d'hora:
>>
>> $ cat /etc/crontab | grep -e daily
>
is Garcia ha escrit:
>> Salut a tothom.
>>
>> Tinc un ordinador sempre engegat que necessito que es reiniciï cada
>> dia ben d'hora:
>>
>> $ cat /etc/crontab | grep -e daily
>> 25 5 * * * root test -x /usr/sbi
Hola,
--- Original Message ---
On Saturday, February 11th, 2023 at 21:34, Josep Lladonosa
wrote:
> He trobat el lloc on hi ha aquestes "de 7:30 h a 23:30 h", a la programació
> del temporitzador de systemd:
>
> $ cat /lib/systemd/system/anacron.timer
> [Unit]
> Description=Trigger
Hola, Narcis:
> He trobat que la comanda "crontab -e" és adequada per a
> modificar i aplicar, però em fa editar un fitxer on només hi ha
> comentaris i cap línia; no sé d'on surt ni on va a parar.
Només serveix per editar els crontabs dels usuaris, no els del
sistema. El
arcis Garcia ha escrit:
>> >> Salut a tothom.
>> >>
>> >> Tinc un ordinador sempre engegat que necessito que es reiniciï cada
>> >> dia ben d'hora:
>> >>
>> >> $ cat /etc/crontab | grep -e daily
>> >> 25 5*
;> El 11/2/23 a les 18:05, Eloi ha escrit:
>> > El 11/2/23 a les 17:24, Narcis Garcia ha escrit:
>> >> Salut a tothom.
>> >>
>> >> Tinc un ordinador sempre engegat que necessito que es reiniciï cada
>> >> dia ben d'hora:
>> >>
&
Garcia del dia ds., 11 de febr.
2023 a les 20:17:
> El 11/2/23 a les 18:05, Eloi ha escrit:
> > El 11/2/23 a les 17:24, Narcis Garcia ha escrit:
> >> Salut a tothom.
> >>
> >> Tinc un ordinador sempre engegat que necessito que es reiniciï cada
> >>
El 11/2/23 a les 18:05, Eloi ha escrit:
El 11/2/23 a les 17:24, Narcis Garcia ha escrit:
Salut a tothom.
Tinc un ordinador sempre engegat que necessito que es reiniciï cada
dia ben d'hora:
$ cat /etc/crontab | grep -e daily
25 5 * * * root test -x /usr/sbin/anacron || ( cd
El 11/2/23 a les 17:24, Narcis Garcia ha escrit:
Salut a tothom.
Tinc un ordinador sempre engegat que necessito que es reiniciï cada
dia ben d'hora:
$ cat /etc/crontab | grep -e daily
25 5 * * * root test -x /usr/sbin/anacron || ( cd / &&
run-parts --report /etc/cr
Salut a tothom.
Tinc un ordinador sempre engegat que necessito que es reiniciï cada dia
ben d'hora:
$ cat /etc/crontab | grep -e daily
25 5 * * * root test -x /usr/sbin/anacron || ( cd / && run-parts
--report /etc/cron.daily )
$ cat /etc/cron.daily/reboot
#!/bin/sh
reboot
Està
Timothy M Butterworth (12022-07-16):
> rc.local does not exist in Debian 11. "/etc/rc.local: No such file or
> directory" should it be a file or a directory?
rc.local is for compatibility with legacy admin practices. Somebody
showed in this thread how it is implemented for systemd. In my opinion,
On Sat, Jul 16, 2022 at 12:06:38PM -0400, Timothy M Butterworth wrote:
> rc.local does not exist in Debian 11. "/etc/rc.local: No such file or
> directory" should it be a file or a directory?
If you wish to use it, it must be a file, with execute permission, and
with a valid shebang (#!/bin/sh).
On Fri, Jul 15, 2022 at 11:07 PM Greg Wooledge wrote:
> On Sat, Jul 16, 2022 at 03:49:09AM +0100, Gareth Evans wrote:
> > $ sudo crontab -l
> > [...]
> > @reboot for f in $(/usr/sbin/zfs list -t snap -o name|grep reboot); do
> /usr/sbin/zfs destroy $f;done
> > @rebo
> On 16 Jul 2022, at 14:39, Anssi Saari wrote:
>
> Tixy writes:
>
>> rc.local is still run on the latest Debian stable. You need to make
>> sure it's a proper executable, i.e. starts with a shebang like
>> '#!/bin/sh' and the file has execute permissions.
>
> Yes and that's because the
Tixy writes:
> rc.local is still run on the latest Debian stable. You need to make
> sure it's a proper executable, i.e. starts with a shebang like
> '#!/bin/sh' and the file has execute permissions.
Yes and that's because the systemd package contains the rc-local.service
which just runs
On Sat, Jul 16, 2022 at 08:13:56AM +0100, Tixy wrote:
> On Sat, 2022-07-16 at 05:30 +0100, Gareth Evans wrote:
> > I was of the impression (which I think it is fair to say has been created)
> > that systemd had done away with /etc/rc.local
>
> rc.local is still run on the latest Debian stable.
On Sat, Jul 16, 2022 at 05:35:39AM +0100, Gareth Evans wrote:
> On Sat 16 Jul 2022, at 05:30, Gareth Evans wrote:
>
> > Why isn't root's $PATH available to root crontab? ie. including the
> > link /sbin -> /usr/sbin?
>
> By which I mean: why can't root cronta
On Sat, 2022-07-16 at 05:30 +0100, Gareth Evans wrote:
> I was of the impression (which I think it is fair to say has been created)
> that systemd had done away with /etc/rc.local
rc.local is still run on the latest Debian stable. You need to make
sure it's a proper executable, i.e. starts with
On Sat 16 Jul 2022, at 05:30, Gareth Evans wrote:
> Why isn't root's $PATH available to root crontab? ie. including the
> link /sbin -> /usr/sbin?
By which I mean: why can't root crontab do everything sudo can do?
Thanks
G
lable to root crontab.
Why isn't root's $PATH available to root crontab? ie. including the link /sbin
-> /usr/sbin?
> "All your crontab entries run in parallel.
OK thanks. Is this documented?
$ man crontab
then
/parallel
[ie search for "parallel"]
returns nothing
On Sat, Jul 16, 2022 at 03:49:09AM +0100, Gareth Evans wrote:
> $ sudo crontab -l
> [...]
> @reboot for f in $(/usr/sbin/zfs list -t snap -o name|grep reboot); do
> /usr/sbin/zfs destroy $f;done
> @reboot /usr/sbin/zfs snap -r rpool@reboot
>
>
> Prepending "/usr
$ sudo crontab -l
[...]
@reboot for f in $(/usr/sbin/zfs list -t snap -o name|grep reboot); do
/usr/sbin/zfs destroy $f;done
@reboot /usr/sbin/zfs snap -r rpool@reboot
Prepending "/usr/sbin/" to "zfs" doesn't make a difference.
Thanks,
Gareth
Hello,
$ sudo crontab -l | grep reboot
[...]
[1] @reboot sleep 10; nmcli c up
[2] @reboot for f in $(zfs list -t snap -o name|grep reboot); do zfs destroy
$f;done
[3] @reboot zfs snap -r rpool@reboot
[1] succeeds, but [2,3] do not.
Any ideas why would be gratefully received.
Many thanks
Buen día lista,
Si es como entiendo y el crontab se encuentra en el mismo servidor
donde se está ejecutando el servicios de publicación del sitio web, en
vez de utilizar curl se puede intentar ejecutar directamente el
archivo *.php desde el crontab haciendo uso del comando php. Por
ejemplo
El mié., 6 de enero de 2021 07:17, miguel angel gonzalez <
mangelgonza...@gmail.com> escribió:
> Hola,
>
> Por descartar, si la programación de los crontab funcionan bien menos esas
> dos tareas,
> ¿has probado a ejecutar esos curl sin crontab? Además, probaría las líneas
&g
Hola,
Por descartar, si la programación de los crontab funcionan bien menos esas
dos tareas,
¿has probado a ejecutar esos curl sin crontab? Además, probaría las líneas
de debug que comentan,
para descartar problemas de sintaxis en los comandos etc, si tienes ese
retardo de 4 minutos a lo mejor
El mar, 5 ene 2021 a las 14:34, Camaleón () escribió:
> El 2021-01-05 a las 14:10 -0300, Fernando Romero escribió:
>
> > El mar, 5 ene 2021 a las 14:04, Camaleón ()
> escribió:
> > > > >
> > > > > > Estoy usando Debian 10 y tengo pr
- Original Message -
> From: "Fernando Romero"
> To: "debian-user-spanish"
> Sent: Tuesday, January 5, 2021 2:10:39 PM
> Subject: Re: problemas con crontab
> El mar, 5 ene 2021 a las 14:04, Camaleón () escribió:
>
>> El 2021-01-05
El 2021-01-05 a las 14:10 -0300, Fernando Romero escribió:
> El mar, 5 ene 2021 a las 14:04, Camaleón () escribió:
> > > >
> > > > > Estoy usando Debian 10 y tengo problemas con el horario en crontab,
> > estoy
> > > > > corriendo un php c
El mar, 5 ene 2021 a las 14:04, Camaleón () escribió:
> El 2021-01-05 a las 09:45 -0300, Fernando Romero escribió:
>
> > El mar, 5 ene 2021 a las 4:16, Camaleón () escribió:
> > >
> > > > Estoy usando Debian 10 y tengo problemas con el horario en crontab,
> est
El 2021-01-05 a las 09:45 -0300, Fernando Romero escribió:
> El mar, 5 ene 2021 a las 4:16, Camaleón () escribió:
> >
> > > Estoy usando Debian 10 y tengo problemas con el horario en crontab, estoy
> > > corriendo un php con curl a cierto horario, pero siempre se ejecut
El mar, 5 ene 2021 a las 4:16, Camaleón () escribió:
> El 2021-01-04 a las 19:05 -0300, Fernando Romero escribió:
>
> > Estoy usando Debian 10 y tengo problemas con el horario en crontab, estoy
> > corriendo un php con curl a cierto horario, pero siempre se ejecuta 4
> &g
El 2021-01-04 a las 19:05 -0300, Fernando Romero escribió:
> Estoy usando Debian 10 y tengo problemas con el horario en crontab, estoy
> corriendo un php con curl a cierto horario, pero siempre se ejecuta 4
> minutos mas tarde, es como que crontab no toma la hora del servidor y esta
&g
Hola como estan.
Estoy usando Debian 10 y tengo problemas con el horario en crontab, estoy
corriendo un php con curl a cierto horario, pero siempre se ejecuta 4
minutos mas tarde, es como que crontab no toma la hora del servidor y esta
usando un horario propio.
A alguien le paso esto?
Saludos
On Mon, Dec 21, 2020 at 12:26:28PM -0500, Gene Heskett wrote:
> On Monday 21 December 2020 10:53:23 to...@tuxteam.de wrote:
>
> > On Mon, Dec 21, 2020 at 09:50:37AM -0500, Gene Heskett wrote:
> > > On Monday 21 December 2020 09:18:45 to...@tuxteam.de wrote:
> >
> > [...]
> >
> > > > I feel dirty
On Mon, Dec 21, 2020 at 10:04:48AM -0600, Nicholas Geovanis wrote:
> On Mon, Dec 21, 2020, 8:19 AM wrote:
>
> > On Mon, Dec 21, 2020 at 03:09:32PM +0100, to...@tuxteam.de wrote:
> >
> > [environment variables and things]
> >
> > Wel, the DCOP docs are here [1] (Ah, Doxygen docs. Is there a
> >
On Monday 21 December 2020 10:53:23 to...@tuxteam.de wrote:
> On Mon, Dec 21, 2020 at 09:50:37AM -0500, Gene Heskett wrote:
> > On Monday 21 December 2020 09:18:45 to...@tuxteam.de wrote:
>
> [...]
>
> > > I feel dirty now.
> >
> > So do I, even that bow legged name generates ill feelings. Me and
On Mon, Dec 21, 2020, 8:19 AM wrote:
> On Mon, Dec 21, 2020 at 03:09:32PM +0100, to...@tuxteam.de wrote:
>
> [environment variables and things]
>
> Wel, the DCOP docs are here [1] (Ah, Doxygen docs. Is there a
> term for "illiterate programming"?).
>
>
The Jesus-freak spirit of Knuth
On Mon, Dec 21, 2020 at 09:50:37AM -0500, Gene Heskett wrote:
> On Monday 21 December 2020 09:18:45 to...@tuxteam.de wrote:
[...]
> > I feel dirty now.
>
> So do I, even that bow legged name generates ill feelings. Me and my
> printer both need a shower. But its better than nothing, and may
>
On Monday 21 December 2020 09:18:45 to...@tuxteam.de wrote:
> On Mon, Dec 21, 2020 at 03:09:32PM +0100, to...@tuxteam.de wrote:
>
> [environment variables and things]
>
> Wel, the DCOP docs are here [1] (Ah, Doxygen docs. Is there a
> term for "illiterate programming"?). Convincing my search
On Mon, Dec 21, 2020 at 03:09:32PM +0100, to...@tuxteam.de wrote:
[environment variables and things]
Wel, the DCOP docs are here [1] (Ah, Doxygen docs. Is there a
term for "illiterate programming"?). Convincing my search engine
to search that site for "environment variable" yields some hits
1 - 100 of 1737 matches
Mail list logo
