Your message dated Fri, 16 Feb 2024 12:07:39 +0100
with message-id <ac31dacf-9ad8-4a1c-8c35-cb6385311...@debian.org>
and subject line Re: Bug#1064043: systemd: /etc/fstab x-systemd.automount mount 
points, x-systemd.idle-timeout changes not effective
has caused the Debian Bug report #1064043,
regarding systemd: /etc/fstab x-systemd.automount mount points, 
x-systemd.idle-timeout changes not effective
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1064043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064043
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 247.3-7+deb11u4
Severity: normal
X-Debbugs-Cc: david.sauv...@adalabs.com

Dear Maintainer,

Having a successful CFIS remote mount point specification using 
x-systemd.automount in /etc/fstab, after the first mount when the 
x-systemd.idle-timeout is changed, and necessary systemd updates run, the old 
idle timeout value is still the effective one, instead of the newly specified 
idle timeout value

Given;
- a successful CFIS remote mount point specification using x-systemd.automount 
in /etc/fstab [0]
- command systemctl daemon-reload executed successfully, and
- command systemctl restart remote-fs.target executed successfully, and
- the resource above has been automatically mounted when needed and unmount 
after the idle timeout at least one time

When;
- the corresponding resource is currently not mounted
- the x-systemd.idle-timeout parameter is changed (i.e from 900 to 60) in the 
/etc/fstab, and
- command systemctl daemon-reload executed successfully, and
- command systemctl restart remote-fs.target executed successfully

Then;
- The effective idle timeout is still the old one (i.e 900) instead of the 
newly specified value (i.e 60)
- The generated file /run/systemd/generator/mnt-resource.mount [3] have the 
correct updated idle timeout value (i.e 60)
- However, corresponding entries in /proc/mounts [1] and /proc/self/mountinfo 
[2] contains the old idle timeout value (i.e 900), which is the effective one, 
and not the newly specified idle timeout value (i.e 60).


[0] /etc/fstab
//W.X.Y.Z/Resource  /mnt/resource  cifs  
noauto,x-systemd.automount,x-systemd.idle-timeout=900,credentials=/dir/my-credentials,dir_mode=0755,file_mode=0644,uid=1000,gid=1000
 0

[1] /proc/mounts
systemd-1 /mnt/resource autofs 
rw,relatime,fd=52,pgrp=1,timeout=900,minproto=5,maxproto=5,direct,pipe_ino=13164
 0 0

[2] /proc/self/mountinfo
82 26 0:32 / /mnt/resource rw,relatime shared:42 - autofs systemd-1 
rw,fd=52,pgrp=1,timeout=900,minproto=5,maxproto=5,direct,pipe_ino=13164

[3] /run/systemd/generator/mnt-resource.mount
# Automatically generated by systemd-fstab-generator

[Unit]
Documentation=man:fstab(5) man:systemd-fstab-generator(8)
SourcePath=/etc/fstab

[Mount]
Where=/mnt/resource
What=//W.X.Y.Z/Resource
Type=cifs
Options=noauto,x-systemd.automount,x-systemd.idle-timeout=60,credentials=/dir/my-credentials,dir_mode=0755,file_mode=0644,uid=1000,gid=1000

-- Package-specific info:

-- System Information:
Debian Release: 11.8
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 
'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-26-amd64 (SMP w/1 CPU thread)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages systemd depends on:
ii  adduser          3.118+deb11u1
ii  libacl1          2.2.53-10
ii  libapparmor1     2.13.6-10
ii  libaudit1        1:3.0-2
ii  libblkid1        2.36.1-8+deb11u1
ii  libc6            2.31-13+deb11u7
ii  libcap2          1:2.44-1
ii  libcrypt1        1:4.4.18-4
ii  libcryptsetup12  2:2.3.7-1+deb11u1
ii  libgcrypt20      1.8.7-6
ii  libgnutls30      3.7.1-5+deb11u3
ii  libgpg-error0    1.38-2
ii  libip4tc2        1.8.7-1
ii  libkmod2         28-1
ii  liblz4-1         1.9.3-2
ii  liblzma5         5.2.5-2.1~deb11u1
ii  libmount1        2.36.1-8+deb11u1
ii  libpam0g         1.4.0-9+deb11u1
ii  libseccomp2      2.5.1-1+deb11u1
ii  libselinux1      3.1-3
ii  libsystemd0      247.3-7+deb11u4
ii  libzstd1         1.4.8+dfsg-2.1
ii  mount            2.36.1-8+deb11u1
ii  util-linux       2.36.1-8+deb11u1

Versions of packages systemd recommends:
ii  dbus                             1.12.28-0+deb11u1
ii  systemd-timesyncd [time-daemon]  247.3-7+deb11u4

Versions of packages systemd suggests:
pn  policykit-1        <none>
pn  systemd-container  <none>

Versions of packages systemd is related to:
pn  dracut           <none>
ii  initramfs-tools  0.140
ii  libnss-systemd   247.3-7+deb11u4
ii  libpam-systemd   247.3-7+deb11u4
ii  udev             247.3-7+deb11u4

-- no debconf information

--- End Message ---
--- Begin Message ---
Am 16.02.24 um 11:43 schrieb David Sauvage:
Package: systemd
Version: 247.3-7+deb11u4
Severity: normal
X-Debbugs-Cc: david.sauv...@adalabs.com

Dear Maintainer,

Having a successful CFIS remote mount point specification using 
x-systemd.automount in /etc/fstab, after the first mount when the 
x-systemd.idle-timeout is changed, and necessary systemd updates run, the old 
idle timeout value is still the effective one, instead of the newly specified 
idle timeout value

Given;
- a successful CFIS remote mount point specification using x-systemd.automount 
in /etc/fstab [0]
- command systemctl daemon-reload executed successfully, and
- command systemctl restart remote-fs.target executed successfully, and
- the resource above has been automatically mounted when needed and unmount 
after the idle timeout at least one time

When;
- the corresponding resource is currently not mounted
- the x-systemd.idle-timeout parameter is changed (i.e from 900 to 60) in the 
/etc/fstab, and
- command systemctl daemon-reload executed successfully, and
- command systemctl restart remote-fs.target executed successfully

You need to restart the affected mount unit mnt-resource.mount, not remote-fs.target, for the changes to be applied.

Regards,
Michael



Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to