gt;Well, but why would you do that. Why isn't it enough to run the fsck
>once before the first mount after each time the device initially
>appeared?
I simply never used automount units, so I had no idea about their
capabilities.
>Lennart
Bye.
Michael.
--
Michael Hirmke
Hi,
>On Sa, 08.09.18 19:10, Michael Hirmke (m...@mike.franken.de) wrote:
[...]
>> For the backup "master" I have the following requirements:
>>
>> - The partition has to be mounted on boot.
>> - It has to be unmounted before the nightly copy job, so that an f
Hi,
>On Mon, 2018-09-10 at 09:55 +0200, Michael Hirmke wrote:
>>
>>>>
>>>>> (I would just use `umount /var/backup`, however.)
>>>>
>>>> Can't do that as long as the mount unit is under systemd control.
>>>> A few seco
quot;noauto" mount option?
This would prevent it from being mounted at startup, which is necessary.
>Martin
Thx and bye.
Michael.
--
Michael Hirmke
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
what I
get when calling "systemctl stop var-backup.mount" - but only
occasionally as I wrote.
>(I would just use `umount /var/backup`, however.)
Can't do that as long as the mount unit is under systemd control.
A few seconds later systemd remounts it on its own.
Bye.
Michael.
--
Mich
sages like "Specified filename /dev/sdf1 has no
mountpoint." when *stopping* var-backup.mount.
I suspect, though, there is a less complicated and perhaps even more
stable approach.
Can anyone lead me on the right way?
TIA.
Bye.
Michael
Hi Zbigniew,
>On Sun, Oct 08, 2017 at 11:22:00AM +0200, Michael Hirmke wrote:
>> Hi,
>>
>> today systemd crashed on my main server:
>>
>> Okt 08 10:06:28 perth systemd[1]: Code should not be reached 'Uh, main
>> process died at wrong time.' a
?
Or is this already fixed in a later version of systemd?
TIA.
Bye.
Michael.
--
Michael Hirmke
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Hi Simon,
>On Fri, 17 Feb 2017 at 19:41:00 +0100, Michael Hirmke wrote:
>> A much better approach is to write a script or program listening for the
>> according signals "PrepareForSleep" and "PrepareForShutdown" on the dbus
>> interface "org.
ggestion regarding a script
listening to the loginmanager signals?
If you are familiar with perl, I could give you my script to adapt it as
you need.
>R.H.
Bye.
Michael.
>On Fri, Feb 17, 2017 at 07:41:00PM +0100, Michael Hirmke wrote:
>> Hi,
>>
>>>Hi,
>>
>
Hi Markus,
>On Friday 11 November 2016 15:13:00 Michael Hirmke wrote:
>> Does anyone know, what "+::" in /etc/passwd means?
>This line is for the NIS client.
thx for the explanation.
>regards
>Markur Köberl
Bye.
Bye.
Hi Simon,
>On Fri, 11 Nov 2016 at 15:13:00 +0100, Michael Hirmke wrote:
>> Does anyone know, what "+::" in /etc/passwd means?
>It's to do with the NSS "compat" plugin, which glues together
>NIS and a traditional password file.
>Look for "Compatibili
Hi Lennart,
>On Fri, 11.11.16 14:41, Michael Hirmke (m...@mike.franken.de) wrote:
>> Hi *,
>>
>> can anyone help me with this error message:
>>
>> systemd-timesyncd[857]: Cannot resolve user name systemd-timesync: No
>> such process
>>
>> Th
time: Fr 2016-11-11 14:40:58 CET
Universal time: Fr 2016-11-11 13:40:58 UTC
RTC time: Fr 2016-11-11 13:40:58
Time zone: Europe/Berlin (CET, +0100)
Network time on: yes
NTP synchronized: no
RTC in local TZ: no
Thx and bye.
Michael.
--
Michael Hirmke
Hi Lennart,
>On Fri, 14.10.16 12:06, Michael Hirmke (camp...@mike.franken.de) wrote:
>> 1. How can I prevent systemd from mounting a manually unmounted
>>partition? The partiton should be mounted automatically during system
>>start, though.
>There w
Hi Karel,
>On Fri, Oct 14, 2016 at 12:06:00PM +0200, Michael Hirmke wrote:
>> Hi *,
>>
>> I've read the man pages and some more documentation about the mount
>> behaviour of systemd, but I couldn't find a definitive answer to my
>> questions.
>> I have
gt;How can I solve this?
it seems to be a very ugly solution, but masking var-backup.mount
before umounting it and unmasking it after remounting works.
Hopefully there are no side effects.
Does anyone know any not so ugly solution?
>[...]
Bye.
Michae
o stops nfsserver
and postfix. Therefore this is not a solution, because in fact both
don't need /var/backup.
How can I solve this?
[...]
Bye.
Michael.
--
Michael Hirmke
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
var-backup.mount" will remount the
>filesystem.
yes, but not changing from read only to read write and back.
>You probably want to avoid "restart" though. :-p
>- Michael
Bye.
Michael.
--
Michael Hirmke
___
systemd-devel mailing l
read only or read write) look
>>like?
>>
>There isn't any. Use `mount`.
Ok.
Bye.
Michael.
--
Michael Hirmke
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
uld switch from mount/umount to pure systemd behaviour for
mounting and unmounting partitons in my script, would a command like
"systemctl stop|start /var/backup" be sufficient?
And how would a remount command (for read only or read write) look
like?
TIA.
Bye.
Michael
k as such. It does
not apply to a certain interface is up, down, activated or deactivated.
If you need the information for the network stack being up or down,
the use of network.target is ok - and works for me.
>Thanks
Bye.
Michael.
--
Michael Hirmke
___
Hi Lennart,
>On Wed, 25.05.16 18:13, Michael Hirmke (m...@mike.franken.de) wrote:
[...]
>> Sorry, I forgot to add information regarding my environment.
>> I use openSuSE Leap 42.1 with a Plasma 5 desktop.
>I don't know if KDE respects these advisory locks and shows them i
rectly (I think the relevant function is
>sysclose()?...)
For the moment I create a handle manually and also open it manually.
Bye.
Michael.
--
Michael Hirmke
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.or
it myself. Now it works as expected.
>>Lennart
Bye.
Michael.
--
Michael Hirmke
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
you have any hint, how I could find that out / debug it?
And there is the fact, that the lock is still in the list of inhibitors.
As far as I understand the docs, the entry should be gone when the fd is
closed.
>Lennart
Bye.
Michael.
--
Michael Hirmke
_
26 matches
Mail list logo
