[systemd-devel] Antw: Re: show journalctl while stopping?
>>> Mantas Mikulenas schrieb am 23.01.2020 um 19:32 in Nachricht : > On Thu, Jan 23, 2020 at 7:36 PM Reindl Harald > wrote: > >> >> >> Am 23.01.20 um 18:32 schrieb Roger Pack: >> > Forgive me if this is too naive, but would it be possible for >> > systemctl to "immediately start outputting logs" (journalctl type >> > output) while it is in the middle of running a command? Ex: while >> > running "systemctl stop my_server" it could show the logs so we could >> > see what is going on? I do miss that from the /etc/init.d days and >> > feel so blind with systemctl now. >> > Thoughts? >> >> and why don't you jsut write a shell alias or simple wrapper for such >> trivial tasks? >> >> frankly "systemctl restart" hast to shut up because otherwise it would >> trigger cron mails and when you have to write a special option anyways >> you can also wirte an alias and be done >> > > I don't think cron jobs are very high on systemctl's priority list. > Certainly lower than interactive use by the sysadmin. And if you actually > have to write a cron job, you can just add --quiet and be done? Similarly: Before bashing the proposal, why not think about an option that will enable that feature? Like "--verbose", "--monitor", "--whatever-you-like"... > > -- > Mantas Mikulėnas ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Antw: Re: show journalctl while stopping?
Am 24.01.20 um 09:45 schrieb Ulrich Windl: Mantas Mikulenas schrieb am 23.01.2020 um 19:32 in > Nachricht > : >> On Thu, Jan 23, 2020 at 7:36 PM Reindl Harald >> wrote: >> >>> >>> >>> Am 23.01.20 um 18:32 schrieb Roger Pack: Forgive me if this is too naive, but would it be possible for systemctl to "immediately start outputting logs" (journalctl type output) while it is in the middle of running a command? Ex: while running "systemctl stop my_server" it could show the logs so we could see what is going on? I do miss that from the /etc/init.d days and feel so blind with systemctl now. Thoughts? >>> >>> and why don't you jsut write a shell alias or simple wrapper for such >>> trivial tasks? >>> >>> frankly "systemctl restart" hast to shut up because otherwise it would >>> trigger cron mails and when you have to write a special option anyways >>> you can also wirte an alias and be done >>> >> >> I don't think cron jobs are very high on systemctl's priority list. >> Certainly lower than interactive use by the sysadmin. And if you actually >> have to write a cron job, you can just add --quiet and be done? > > Similarly: Before bashing the proposal, why not think about an option that > will enable that feature? Like "--verbose", "--monitor", > "--whatever-you-like".. i got annoyed by "I do miss that from the /etc/init.d days and feel so blind with systemctl now" which is nonsense sysvinit didn't even have the informations to show logs belonging to a service ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] homed, LUKS2 passphrase encoding, and recovery key
could cryptsetup be "insensitive" to the configured keyboard layout and adopt/toggle the US/ASCII layout ? as the physical keys on the keyboard do not move ;-), the end user would enter the password he wants and cryptsetup would only receive ASCII characters... let's say I use "zézé" (french keyboard) as a password : well for me, as an end user, changing context doesn't change anything, I always press the same keys [Z] and [é2~] and I always think my password is "zézé", but the password that protects my data is in fact w2w2. Le ven. 24 janv. 2020 à 05:30, Andrei Borzenkov a écrit : > 24.01.2020 06:56, Alexander E. Patrakov пишет: > >> > >> I assume users want their login passphrase to use local characters. > > > > That's just an assumption, with no data presented to back it up. > > > > I have seen enough cases when users memorized Russian passwords and > entered ASCII characters based on keyboard layout mapping (they actually > mentally entered *Cyrillic* characters). I do not have any > scientifically relevant data though. > ___ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/systemd-devel > ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] homed, LUKS2 passphrase encoding, and recovery key
On Fri, Jan 24, 2020 at 11:42 AM Pascal wrote: > could cryptsetup be "insensitive" to the configured keyboard layout and > adopt/toggle the US/ASCII layout ? > as the physical keys on the keyboard do not move ;-), the end user would > enter the password he wants and cryptsetup would only receive ASCII > characters... > The CLI tool cannot do that, as it only receives text and not actual keypresses. So while this would be possible in the initramfs unlocker (just delay loadkeys until after unlocking), it wouldn't be possible when creating volumes or changing passphrases via Xterm or SSH. X11 programs *might* be able to do that, but I have a feeling it'd be a bit kludgy and unreliable... And either way, it would mean a passphrase entered via X11 couldn't be used via CLI and vice versa. -- Mantas Mikulėnas ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] making journald logs persistent on raspberry pi
It's quite common on the Raspberry Pi to make /var/log a tmpfs, in order to reduce the number of writes to the SD card that is the pi's main storage. That's quite acceptable for most logs but I'd like to make journald's logs persistent so I'll be able to investigate any problems that occur whilst booting or shutting down more easily. My first thought was to configure journald to write the log somewhere else, but it seems there's no possibility to do that? (why not?) So I think I will need to create /var/log/journal as a symlink to a directory in a permanent filesystem. The symlink needs to be created after the tmpfs is created but before journald starts (or else journald will need to be told to notice the change). My systemd foo isn't up to that and a web search hasn't found an answer. What's the best way to do it please? TIA, Dave ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Antw: Re: show journalctl while stopping?
Am Fr., 24. Jan. 2020 um 09:45 Uhr schrieb Ulrich Windl : > Similarly: Before bashing the proposal, why not think about an option that > will enable that feature? Like "--verbose", "--monitor", > "--whatever-you-like"... There you go https://github.com/systemd/systemd/blob/master/TODO#L891 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] making journald logs persistent on raspberry pi
On Fri, Jan 24, 2020 at 5:32 PM Dave Howorth wrote: > It's quite common on the Raspberry Pi to make /var/log a tmpfs, in > order to reduce the number of writes to the SD card that is the pi's > main storage. That's quite acceptable for most logs but I'd like to > make journald's logs persistent so I'll be able to investigate any > problems that occur whilst booting or shutting down more easily. > > My first thought was to configure journald to write the log somewhere > else, but it seems there's no possibility to do that? (why not?) > > So I think I will need to create /var/log/journal as a symlink to a > directory in a permanent filesystem. The symlink needs to be created > after the tmpfs is created but before journald starts (or else journald > will need to be told to notice the change). > > My systemd foo isn't up to that and a web search hasn't found an answer. > What's the best way to do it please? > Mount --bind a persistent directory on top of /var/log/journal, using the same method that you currently use for mounting the tmpfs. -- Mantas Mikulėnas ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] dbus activation service path
Hello! Thank you for all the great work! Can't wait to test systemd-homed. I also have a question about dbus activation. Is there an environment variable or something to tell systemd/dbus-broker &co to look in a specific path for dbus .service files? I have a .desktop file which requires dbus activation but the .service can not be in any standard path and I want to let the .desktop file know where to look for the dbus .service file. Any suggestions? br, Damian ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
