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
On Tue 27 Feb 2024 at 15:35:07 (+), Michael Kjörling wrote:
> On 27 Feb 2024 10:15 -0500, from g...@extremeground.com (Gary Dale):
> In this case you might even want the second to execute only when the
> first completes _successfully_, so:
>
> @reboot /usr/sbin/modprobe brcmfmac && echo 13b1
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 extra characters (perhaps
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.
>>>
>>>ls -l /root/cron*
>>> ls: cannot access '/root/cron*': No such
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,
On 2024-02-27 10:32, Greg Wooledge wrote:
On Tue, Feb 27, 2024 at 10:15:59AM -0500, Gary Dale wrote:
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 >
On 2024-02-27 10:25, Kushal Kumaran wrote:
On Tue, Feb 27 2024 at 10:15:59 AM, Gary Dale wrote:
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 >
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:
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 fails. I get an e-mail
On Tue, Feb 27, 2024 at 10:15:59AM -0500, Gary Dale wrote:
> 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
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/crontab /etc/crontab
On Tue, Feb 27 2024 at 10:15:59 AM, Gary Dale wrote:
> 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
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
@reboot
28 matches
Mail list logo
