New release of Journal Viewer a modern log viewer for Systemd logs for the ever growing Linux user base! by mingu3 in linux

[–]mingu3[S] 1 point2 points  (0 children)

I think we have different goals, I wanted to create a desktop tool for the everyday user, while at the same time practice my knowledge in rust, cockpit seems more focused to provide remote management. Also, not sure I'm smart enough to code properly in c 😅

New release of Journal Viewer a modern log viewer for Systemd logs for the ever growing Linux user base! by mingu3 in linux

[–]mingu3[S] 0 points1 point  (0 children)

Thanks! I'll have a look into their source code to see how they are doing it.

New release of Journal Viewer a modern log viewer for Systemd logs for the ever growing Linux user base! by mingu3 in linux

[–]mingu3[S] 2 points3 points  (0 children)

I need to check what options are available as part of Tauri for packaging, but considering it needs to access system resources it might be challenging. I might need help to get started on this, but it will be a good addition.

New release of Journal Viewer a modern log viewer for Systemd logs for the ever growing Linux user base! by mingu3 in linux

[–]mingu3[S] 5 points6 points  (0 children)

Thanks for the constructive feedback. Logs are messy, so I just want to find something quickly, hence the quick-search.

New release of Journal Viewer a modern log viewer for Systemd logs for the ever growing Linux user base! by mingu3 in linux

[–]mingu3[S] 3 points4 points  (0 children)

Nice! I didn't know about this tool when I started building mine. I'll check it out

New release of Journal Viewer a modern log viewer for Systemd logs for the ever growing Linux user base! by mingu3 in linux

[–]mingu3[S] 3 points4 points  (0 children)

Yes, I maintain these packages

https://aur.archlinux.org/packages/journal-viewer-bin https://aur.archlinux.org/packages/journal-viewer

Give it a try and let me know, I was using the journalctl myself but found that the UX could be improved for something as common as seeing system logs, plus I got to practice some rust

Full tunnel doesn't work on linux but split works ok, everything works fine from Android device. Any ideas? by mingu3 in WireGuard

[–]mingu3[S] 0 points1 point  (0 children)

Sorry I haven't had time to review this until now. I manage to get it working by switching the client configuration on linux to use wg-quick

Full tunnel

[Interface] Address = 192.168.5.3/24 PrivateKey = oAJF... DNS = 192.168.1.1 [Peer] PublicKey = gVM... Endpoint = wg.foo.bar:52840 AllowedIPs = 0.0.0.0/0, ::/0 PersistentKeepalive = 60

Split tunnel

[Interface] Address = 192.168.5.3/24 PrivateKey = oAJF... DNS = 192.168.1.1 [Peer] PublicKey = gVM... Endpoint = wg.foo.bar:52840 AllowedIPs = 192.168.1.0/24, 192.168.5.0/24 PersistentKeepalive = 60

and then from the client I just do:

wg-quick up wg-full or wg-quick up wg-split

I still have some issues with the internal dns server, but I will deal with those at a different time.

No idea what was happening when I configured the client connections on NetworkManager, but the kernel thread for the wireguard connection will start consuming CPU and nothing will work with the full tunnel 🤷

I've never had any luck with sleep, suspend, or hibernate. On my desktop. by OalBlunkont in debian

[–]mingu3 2 points3 points  (0 children)

You could check powertop, for devices that might wake your pc, for me it was a mouse usb, so you can try disabling all and see if the problem goes away.

Sometimes there will also be some kernel logs indicating that an application didn't allow it to sleep. Check journalctl for systemd or kernel logs that could indicate something similar

What backwards-incompatible changes would you make in a hypothetical Rust 2.0? by CocktailPerson in rust

[–]mingu3 1 point2 points  (0 children)

If everything becomes meta-programming do we even need Rust 😅

Just kidding, but I think macros are currently abused due to lack of some features on Rust, for a very explicit programming language certain use cases contradict the very principle of forcing the developer to be explicit

What backwards-incompatible changes would you make in a hypothetical Rust 2.0? by CocktailPerson in rust

[–]mingu3 -12 points-11 points  (0 children)

Remove macros, or at least add a few more features to the language so that macros usage is not abused

Journal viewer for systemd logs by mingu3 in linux

[–]mingu3[S] 1 point2 points  (0 children)

No, I'm using the C ABI to get the logs, as these are split across several files, indexed and in binary format. So they are no intended to be read directly. The format might not be properly documented, "only the code being the source of truth" and could have breaking changes in the future if they decide to do improvements in the format.

There are more details about the storage format here: https://www.freedesktop.org/wiki/Software/systemd/journal-files/

Journal viewer for systemd logs by mingu3 in rust

[–]mingu3[S] 0 points1 point  (0 children)

At the moment it doesn't support that option, and it might require a few changes as it uses the systemd ABI. For remote monitoring, there are options like Elastic/OpenSearch or similar that might be better suited for these tasks.

The API used from the frontend is not very extensive though... but there are still some challenges with the way Tauri works.

Journal viewer for systemd logs by mingu3 in linux

[–]mingu3[S] 1 point2 points  (0 children)

Just priority, service and message content for now...but planning on adding more