Michael Jones [2020-05-13 12:48:49]:
Hi,
> I have a critical service on my OpenWRT system that needs monitoring and
> re-starting if it's failed.
whats wrong with monit[1]? It was designed exactly for this purpose and is
much more flexible.
> I've been looking for a mechanism in procd that wou
On Thu, May 14, 2020, 23:43 Philip Prindeville <
philipp_s...@redfish-solutions.com> wrote:
>
> > On May 13, 2020, at 11:48 AM, Michael Jones
> wrote:
> >
> > I have a critical service on my OpenWRT system that needs monitoring and
> re-starting if it's failed.
> >
> > I've been looking for a mec
> On May 13, 2020, at 11:48 AM, Michael Jones wrote:
>
> I have a critical service on my OpenWRT system that needs monitoring and
> re-starting if it's failed.
>
> I've been looking for a mechanism in procd that would allow me to request
> that my service be terminated if it did not periodic
Philip Prindeville wrote:
>> In general, I think that this decision needs to up-leveled to as a
>> build option. There are many cases where I would agree: you want the
>> box to die rather than potentially come up insecurely.
> A while ago I posted an option to “bake in” a defau
What should I use instead of strlcpy or strcpy?
Sent from my iPhone
> On May 14, 2020, at 11:04 AM, Jo-Philipp Wich wrote:
>
> Hi,
>
> the sprintf() to snprintf() changes are fine to me. Please omit the
> conversions to strlcpy() and please don't use fmemopen().
>
> ~ Jo
>
> ___
FWIW, k8s has Liveness, Readiness and Startup Probes
https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/
::
> The kubelet uses startup probes to know when a container application has
started. If such a probe is configured, it disables liveness and
> On May 14, 2020, at 8:23 AM, Michael Richardson wrote:
>
> [snip]
>
> It depends a lot on the relative cost of sending a service person there to
> repair the device (push the button, reflash or replace the device), vs the
> risk of the box not operating at all.
>
> In the NAT44 home router
Hi,
the sprintf() to snprintf() changes are fine to me. Please omit the
conversions to strlcpy() and please don't use fmemopen().
~ Jo
signature.asc
Description: OpenPGP digital signature
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
Hi,
I like the ubus watchdog ping/pong idea.
~ Jo
signature.asc
Description: OpenPGP digital signature
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Philip Prindeville wrote:
>> A reboot with some logging on disk would allow for remote sysupgrades
>> to have some kind of recoverability.
> What if the failure left the box in a partially compromised state?
> Would you want your firewall to “fail open”? I wouldn’t.
It depends
This tidies up the ethernet node in mt7620 DTS files by:
- removing unnecessary status as it is not disabled
- reordering properties consistently
- adding empty lines to enhance readability
This should make comparison and reviewing new PRs based on C/P easier.
Signed-off-by: Adrian Schmutzler
-
The property "ralink,port-map" never existed, and the device is a
one-port anyway. Just remove it.
Fixes: 5ef79af4f80f ("ramips: add support for Ravpower WD03")
Signed-off-by: Adrian Schmutzler
---
target/linux/ramips/dts/mt7620n_ravpower_wd03.dts | 1 -
1 file changed, 1 deletion(-)
diff --gi
Hi adrian,
However, if you need a separate factory for u-boot now, go for it. But then,
I'd prefer it to have the .bin extension as well.
--->In the uboot of gl-e750, the extension .bin is considered to be nor
firmware and will be handled according to the upgrade process of nor firmware.
--->The
Hi,
> > +&wmac {
> > + status = "okay";
> > + mtd-cal-data = <&art 0x1000>;
> > + mtd-mac-address = <&art 0x1002>;
>
> mtd-mac-address can be dropped here, as it will be read from this offset by
> mtd-cal-data automatically.
> ---> Will the offset of 0x2 be automatically added?
If you read cald
Hi,adrian
I added a reply below your question.
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> On Behalf Of Luochongjun
> Sent: Donnerstag, 7. Mai 2020 13:47
> To: openwrt-devel@lists.openwrt.org
> Cc: Luochongjun
> Subject: [OpenWrt-Devel]
Hi,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> On Behalf Of Luochongjun
> Sent: Donnerstag, 7. Mai 2020 13:47
> To: openwrt-devel@lists.openwrt.org
> Cc: Luochongjun
> Subject: [OpenWrt-Devel] [PATCH] ath79: add support for gl-e750
>
> T
On 07.05.20 13:46, Luochongjun wrote:
The gl-e750 is a portable travel router that gives you safe access to
the internet while traveling.
Specifications:
- SoC: Qualcomm Atheros AR9531 (650MHz)
- RAM: 128 MB DDR2
- Flash: 16 MB SPI NOR (W25Q128FVSG) + 128 MB SPI NAND (GD5F1GQ4UFYIG)
- Ethernet:
On 07.05.20 13:46, Luochongjun wrote:
The gl-e750 is a portable travel router that gives you safe access to
the internet while traveling.
Specifications:
- SoC: Qualcomm Atheros AR9531 (650MHz)
- RAM: 128 MB DDR2
- Flash: 16 MB SPI NOR (W25Q128FVSG) + 128 MB SPI NAND (GD5F1GQ4UFYIG)
- Ethernet
Hi all,
We're using Openwrt 19.07.2 on the Archer C7 V5 for a client project, and
have hit an issue that's blocking our development.
Given our tight timelines on this project, we'd be very open to paying
someone with ath9k experience to help us resolve this on a contract basis.
We're based in Lon
19 matches
Mail list logo
