[Touch-packages] [Bug 40189] Re: [SRU] [xenial] [bionic] autofs needs to be restarted to pick up some shares
Ubuntu 18.04.1 with autofs version 5.1.2-1ubuntu3 --> Still the same problem. Service restart is required to get autofs to work. How could I help to triage this bug? What information are needed to help reproduce it so it could be fixed? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/40189 Title: [SRU] [xenial] [bionic] autofs needs to be restarted to pick up some shares Status in autofs package in Ubuntu: Fix Released Status in autofs5 package in Ubuntu: Invalid Status in upstart package in Ubuntu: Invalid Status in autofs source package in Xenial: Incomplete Bug description: I am using autofs to access shares on a Windows XP machine from a Kubuntu AMD64 machine. The problems applies in both Breezy and Dapper. EDIT: confirmed with similar configuration on Intrepid with a NetApp filer hosting NFS. Server OS removed from summary. When I first try to access the mount point via cd or in Konqueror it does not exist. However, if I then restart autofs (/etc/init.d/autofs restart) everythin then works OK. My config files are: auto.master # # $Id: auto.master,v 1.3 2003/09/29 08:22:35 raven Exp $ # # Sample auto.master file # This is an automounter map and it has the following format # key [ -mount-options-separated-by-comma ] location # For details of the format look at autofs(5). #/misc/etc/auto.misc --timeout=60 #/misc/etc/auto.misc #/net /etc/auto.net /petunia /etc/petunia.misc --timeout=60 petunia.misc # # $Id: auto.misc,v 1.2 2003/09/29 08:22:35 raven Exp $ # # This is an automounter map and it has the following format # key [ -mount-options-separated-by-comma ] location # Details may be found in the autofs(5) manpage cd -fstype=iso9660,ro,nosuid,nodev :/dev/cdrom tony -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/tony chris -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/chris shared-fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/SharedDocs linuxbackups -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/linuxbackups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/40189/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1771340] Re: sshd failed on config reload
@ahasenack, of course I could double check. I've done so a few minutes ago and you are right. After trying to reload with a corrupted config file the reload failed but the service is still up and running. Please see the following output for confirmation: ~~~ root@vbox-xenial:~# systemctl status sshd ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: active (running) since Do 2018-10-11 11:13:35 CEST; 2min 19s ago Main PID: 8917 (sshd) CGroup: /system.slice/ssh.service └─8917 /usr/sbin/sshd -D Okt 11 11:13:35 vbox-xenial systemd[1]: Starting OpenBSD Secure Shell server... Okt 11 11:13:35 vbox-xenial sshd[8917]: Server listening on 0.0.0.0 port 22. Okt 11 11:13:35 vbox-xenial sshd[8917]: Server listening on :: port 22. Okt 11 11:13:35 vbox-xenial systemd[1]: Started OpenBSD Secure Shell server. root@vbox-xenial:~# echo "blah blah" >>/etc/ssh/sshd_config root@vbox-xenial:~# systemctl reload sshd Job for ssh.service failed because the control process exited with error code. See "systemctl status ssh.service" and "journalctl -xe" for details. root@vbox-xenial:~# systemctl status sshd ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: active (running) (Result: exit-code) since Do 2018-10-11 11:13:35 CEST; 2min 51s ago Process: 9033 ExecReload=/usr/sbin/sshd -t (code=exited, status=255) Main PID: 8917 (sshd) CGroup: /system.slice/ssh.service └─8917 /usr/sbin/sshd -D Okt 11 11:13:35 vbox-xenial systemd[1]: Starting OpenBSD Secure Shell server... Okt 11 11:13:35 vbox-xenial sshd[8917]: Server listening on 0.0.0.0 port 22. Okt 11 11:13:35 vbox-xenial sshd[8917]: Server listening on :: port 22. Okt 11 11:13:35 vbox-xenial systemd[1]: Started OpenBSD Secure Shell server. Okt 11 11:16:15 vbox-xenial systemd[1]: Reloading OpenBSD Secure Shell server. Okt 11 11:16:15 vbox-xenial sshd[9033]: /etc/ssh/sshd_config: line 89: Bad configuration option: blah Okt 11 11:16:15 vbox-xenial sshd[9033]: /etc/ssh/sshd_config: terminating, 1 bad configuration options Okt 11 11:16:15 vbox-xenial systemd[1]: ssh.service: Control process exited, code=exited status=255 Okt 11 11:16:15 vbox-xenial systemd[1]: Reload failed for OpenBSD Secure Shell server. root@vbox-xenial:~# ~~~ Sorry, that I didn't get it in the first try. The update looks fine for my, too. ** Tags removed: verification-failed-xenial verification-needed ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1771340 Title: sshd failed on config reload Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Xenial: Fix Committed Status in openssh package in Debian: Fix Released Bug description: [Impact] sshd doesn't check the configuration when reloading. If a user generates an invalid configuration file, sshd will shut down and not come back up when the user issues a reload. [Test Case] $ lxc launch ubuntu:xenial tester $ lxc exec tester bash # echo "blah blah" >>/etc/ssh/sshd_config # systemctl reload sshd Job for ssh.service failed because the control process exited with error code. See "systemctl status ssh.service" and "journalctl -xe" for details. # systemctl status ssh.service ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2018-08-21 18:15:41 UTC; 19s ago * The service should have checked the config file, failed to reload, but remained active in its current configuration. In this case ssh has shut down. [Regression Potential] This code will only trigger on an invalid configuration file (in which case sshd would not load anyway), so there should be no regressions. [Other Info] autopkgtest [13:45:46]: test regress: ---] autopkgtest [13:45:47]: test regress: - - - - - - - - - - results - - - - - - - - - - regress PASS autopkgtest [13:45:47]: summary regress PASS [Original Description] After adding some lines to /etc/ssh/sshd_config I tried to reload the configuration with the command: ``` sudo systemctl reload sshd ``` No error message was returned. So I assumed that the sshd was running with the current config. But `sudo systemctl status sshd` told me that the service failed due to a wrong option in /etc/ssh/sshd_config. Please see the following output: ~~~ :~$ sudo vim /etc/ssh/sshd_config :~$ sudo systemctl reload sshd :~$ sudo systemctl status sshd ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled;
[Touch-packages] [Bug 1771340] Re: sshd failed on config reload
Hi there, I tested version 1:7.2p2-4ubuntu2.5 from proposed but the issue still exists. Behavior is exactly as before. Regards, Tronde ** Tags removed: verification-needed-xenial ** Tags added: verification-failed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1771340 Title: sshd failed on config reload Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Xenial: Fix Committed Status in openssh package in Debian: Fix Released Bug description: [Impact] sshd doesn't check the configuration when reloading. If a user generates an invalid configuration file, sshd will shut down and not come back up when the user issues a reload. [Test Case] $ lxc launch ubuntu:xenial tester $ lxc exec tester bash # echo "blah blah" >>/etc/ssh/sshd_config # systemctl reload sshd Job for ssh.service failed because the control process exited with error code. See "systemctl status ssh.service" and "journalctl -xe" for details. # systemctl status ssh.service ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2018-08-21 18:15:41 UTC; 19s ago * The service should have checked the config file, failed to reload, but remained active in its current configuration. In this case ssh has shut down. [Regression Potential] This code will only trigger on an invalid configuration file (in which case sshd would not load anyway), so there should be no regressions. [Other Info] autopkgtest [13:45:46]: test regress: ---] autopkgtest [13:45:47]: test regress: - - - - - - - - - - results - - - - - - - - - - regress PASS autopkgtest [13:45:47]: summary regress PASS [Original Description] After adding some lines to /etc/ssh/sshd_config I tried to reload the configuration with the command: ``` sudo systemctl reload sshd ``` No error message was returned. So I assumed that the sshd was running with the current config. But `sudo systemctl status sshd` told me that the service failed due to a wrong option in /etc/ssh/sshd_config. Please see the following output: ~~~ :~$ sudo vim /etc/ssh/sshd_config :~$ sudo systemctl reload sshd :~$ sudo systemctl status sshd ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Di 2018-05-15 10:00:04 CEST; 8s ago Process: 12089 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS) Process: 7536 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255) Main PID: 7536 (code=exited, status=255) ~~~ I would expect that a warning or error message is returned when the service fails while reloading it's configuration. A fix for this behaviour would be appreciated. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.4 ProcVersionSignature: Ubuntu 3.13.0-112.159-generic 3.13.11-ckt39 Uname: Linux 3.13.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 Date: Tue May 15 10:18:25 2018 InstallationDate: Installed on 2013-01-10 (1950 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) SourcePackage: openssh UpgradeStatus: Upgraded to xenial on 2017-03-12 (428 days ago) mtime.conffile..etc.pam.d.sshd: 2017-03-13T19:59:01.965420 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1771340/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1771340] Re: sshd failed on config reload
This bug seems to be fixed upstream in a newer version: [Debian Bug report logs - #865770 openssh-server fails to validate configuration before reloading, under systemd](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865770) Maybe it is possible to get a version update in Xenial?! ** Bug watch added: Debian Bug tracker #865770 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865770 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1771340 Title: sshd failed on config reload Status in openssh package in Ubuntu: New Bug description: After adding some lines to /etc/ssh/sshd_config I tried to reload the configuration with the command: ``` sudo systemctl reload sshd ``` No error message was returned. So I assumed that the sshd was running with the current config. But `sudo systemctl status sshd` told me that the service failed due to a wrong option in /etc/ssh/sshd_config. Please see the following output: ~~~ :~$ sudo vim /etc/ssh/sshd_config :~$ sudo systemctl reload sshd :~$ sudo systemctl status sshd ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Di 2018-05-15 10:00:04 CEST; 8s ago Process: 12089 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS) Process: 7536 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255) Main PID: 7536 (code=exited, status=255) ~~~ I would expect that a warning or error message is returned when the service fails while reloading it's configuration. A fix for this behaviour would be appreciated. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.4 ProcVersionSignature: Ubuntu 3.13.0-112.159-generic 3.13.11-ckt39 Uname: Linux 3.13.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 Date: Tue May 15 10:18:25 2018 InstallationDate: Installed on 2013-01-10 (1950 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) SourcePackage: openssh UpgradeStatus: Upgraded to xenial on 2017-03-12 (428 days ago) mtime.conffile..etc.pam.d.sshd: 2017-03-13T19:59:01.965420 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1771340/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1771340] [NEW] sshd failed on config reload
Public bug reported: After adding some lines to /etc/ssh/sshd_config I tried to reload the configuration with the command: ``` sudo systemctl reload sshd ``` No error message was returned. So I assumed that the sshd was running with the current config. But `sudo systemctl status sshd` told me that the service failed due to a wrong option in /etc/ssh/sshd_config. Please see the following output: ~~~ :~$ sudo vim /etc/ssh/sshd_config :~$ sudo systemctl reload sshd :~$ sudo systemctl status sshd ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Di 2018-05-15 10:00:04 CEST; 8s ago Process: 12089 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS) Process: 7536 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255) Main PID: 7536 (code=exited, status=255) ~~~ I would expect that a warning or error message is returned when the service fails while reloading it's configuration. A fix for this behaviour would be appreciated. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.4 ProcVersionSignature: Ubuntu 3.13.0-112.159-generic 3.13.11-ckt39 Uname: Linux 3.13.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 Date: Tue May 15 10:18:25 2018 InstallationDate: Installed on 2013-01-10 (1950 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) SourcePackage: openssh UpgradeStatus: Upgraded to xenial on 2017-03-12 (428 days ago) mtime.conffile..etc.pam.d.sshd: 2017-03-13T19:59:01.965420 ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1771340 Title: sshd failed on config reload Status in openssh package in Ubuntu: New Bug description: After adding some lines to /etc/ssh/sshd_config I tried to reload the configuration with the command: ``` sudo systemctl reload sshd ``` No error message was returned. So I assumed that the sshd was running with the current config. But `sudo systemctl status sshd` told me that the service failed due to a wrong option in /etc/ssh/sshd_config. Please see the following output: ~~~ :~$ sudo vim /etc/ssh/sshd_config :~$ sudo systemctl reload sshd :~$ sudo systemctl status sshd ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Di 2018-05-15 10:00:04 CEST; 8s ago Process: 12089 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS) Process: 7536 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255) Main PID: 7536 (code=exited, status=255) ~~~ I would expect that a warning or error message is returned when the service fails while reloading it's configuration. A fix for this behaviour would be appreciated. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.4 ProcVersionSignature: Ubuntu 3.13.0-112.159-generic 3.13.11-ckt39 Uname: Linux 3.13.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 Date: Tue May 15 10:18:25 2018 InstallationDate: Installed on 2013-01-10 (1950 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) SourcePackage: openssh UpgradeStatus: Upgraded to xenial on 2017-03-12 (428 days ago) mtime.conffile..etc.pam.d.sshd: 2017-03-13T19:59:01.965420 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1771340/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 40189] Re: [SRU] [xenial] autofs needs to be restarted to pick up some shares
Good Moring, I would like to add some news. I have removed and purged autofs from one of my Thinkpads and installed autofs 5.1.2-1 from Bionic in Xenial. I have used the packages from http://archive.ubuntu.com/ubuntu/pool/main/a/autofs/autofs_5.1.2-1ubuntu2_amd64.de Surprise, the behaviour is exactly the same as in version 5.1.1. It won't work until the autofs.service is restarted. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/40189 Title: [SRU] [xenial] autofs needs to be restarted to pick up some shares Status in autofs package in Ubuntu: Fix Released Status in autofs5 package in Ubuntu: Invalid Status in upstart package in Ubuntu: Invalid Status in autofs source package in Xenial: Incomplete Bug description: I am using autofs to access shares on a Windows XP machine from a Kubuntu AMD64 machine. The problems applies in both Breezy and Dapper. EDIT: confirmed with similar configuration on Intrepid with a NetApp filer hosting NFS. Server OS removed from summary. When I first try to access the mount point via cd or in Konqueror it does not exist. However, if I then restart autofs (/etc/init.d/autofs restart) everythin then works OK. My config files are: auto.master # # $Id: auto.master,v 1.3 2003/09/29 08:22:35 raven Exp $ # # Sample auto.master file # This is an automounter map and it has the following format # key [ -mount-options-separated-by-comma ] location # For details of the format look at autofs(5). #/misc/etc/auto.misc --timeout=60 #/misc/etc/auto.misc #/net /etc/auto.net /petunia /etc/petunia.misc --timeout=60 petunia.misc # # $Id: auto.misc,v 1.2 2003/09/29 08:22:35 raven Exp $ # # This is an automounter map and it has the following format # key [ -mount-options-separated-by-comma ] location # Details may be found in the autofs(5) manpage cd -fstype=iso9660,ro,nosuid,nodev :/dev/cdrom tony -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/tony chris -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/chris shared-fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/SharedDocs linuxbackups -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/linuxbackups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/40189/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 40189] Re: [SRU] [xenial] autofs needs to be restarted to pick up some shares
Hello,
It's me again. So with today I've checked with three different hosts.
All running Xenial with autofs 5.1.1-1ubuntu3.1 and Kernel
4.4.0-116-generic. The host are a Thinkpad T410, X201 and a VirtualBox
guest system.
While the VirtualBox guest system works just fine, the autofs on the
Thinkpads did not work directly after boot. The autofs.service needs to
be restarted first in order to get autofs to work.
I have used tcpdump an strace to get some better look on what is
happening on the Thinkpads. So I did the following:
1. Boot Thinkpad
2. Setup tcpdump/wireshark snoop
3. Check that autofs is running with `sudo systemctl status autofs.service`
4. Run `strace ls -ld $MOUNTPOINT` where $MOUNTPOINT is the automounter share
from automounter map
In strace I see:
lstat("$MOUNTPOINT", 0x14861a0) = -1 ENOENT (No such file or directory)
The snoop shows that no single packet goes over the network to the NAS.
Next step:
5. Run `sudo systemctl status autofs.service`
6. Run `strace ls -ld $MOUNTPOINT` where $MOUNTPOINT is the automounter share
from automounter map
Now, in strace I see:
lstat("$MOUNTPOINT", {st_mode=S_IFDIR|0777, st_size=0, ...}) = 0
And in the snoop I see the expected packages crossing the network.
That's it. I do not know what else I could do to help with this matter.
If you need additional information tell me what you need, please.
Regards,
Tronde
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/40189
Title:
[SRU] [xenial] autofs needs to be restarted to pick up some shares
Status in autofs package in Ubuntu:
Fix Released
Status in autofs5 package in Ubuntu:
Invalid
Status in upstart package in Ubuntu:
Invalid
Status in autofs source package in Xenial:
Incomplete
Bug description:
I am using autofs to access shares on a Windows XP machine from a
Kubuntu AMD64 machine. The problems applies in both Breezy and
Dapper.
EDIT: confirmed with similar configuration on Intrepid with a NetApp
filer hosting NFS. Server OS removed from summary.
When I first try to access the mount point via cd or in Konqueror it
does not exist. However, if I then restart autofs
(/etc/init.d/autofs restart) everythin then works OK. My config files
are:
auto.master
#
# $Id: auto.master,v 1.3 2003/09/29 08:22:35 raven Exp $
#
# Sample auto.master file
# This is an automounter map and it has the following format
# key [ -mount-options-separated-by-comma ] location
# For details of the format look at autofs(5).
#/misc/etc/auto.misc --timeout=60
#/misc/etc/auto.misc
#/net /etc/auto.net
/petunia /etc/petunia.misc --timeout=60
petunia.misc
#
# $Id: auto.misc,v 1.2 2003/09/29 08:22:35 raven Exp $
#
# This is an automounter map and it has the following format
# key [ -mount-options-separated-by-comma ] location
# Details may be found in the autofs(5) manpage
cd -fstype=iso9660,ro,nosuid,nodev :/dev/cdrom
tony -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777
://192.168.1.2/tony
chris -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777
://192.168.1.2/chris
shared-fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777
://192.168.1.2/SharedDocs
linuxbackups -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777
://192.168.1.2/linuxbackups
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/40189/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 40189] Re: [SRU] [xenial] autofs needs to be restarted to pick up some shares
Ok, I'm lost. Today I've checked in another Xenial with autofs 5.1.1-1ubuntu3.1. Kernel is 4.4.0-116-generic as in the system of my last post. But in this system I have to restart autofs.service each time after a (re)boot otherwise I cannot access the shares. I really don't get it. Maybe some other users could try to reproduce the problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/40189 Title: [SRU] [xenial] autofs needs to be restarted to pick up some shares Status in autofs package in Ubuntu: Fix Released Status in autofs5 package in Ubuntu: Invalid Status in upstart package in Ubuntu: Invalid Status in autofs source package in Xenial: Incomplete Bug description: I am using autofs to access shares on a Windows XP machine from a Kubuntu AMD64 machine. The problems applies in both Breezy and Dapper. EDIT: confirmed with similar configuration on Intrepid with a NetApp filer hosting NFS. Server OS removed from summary. When I first try to access the mount point via cd or in Konqueror it does not exist. However, if I then restart autofs (/etc/init.d/autofs restart) everythin then works OK. My config files are: auto.master # # $Id: auto.master,v 1.3 2003/09/29 08:22:35 raven Exp $ # # Sample auto.master file # This is an automounter map and it has the following format # key [ -mount-options-separated-by-comma ] location # For details of the format look at autofs(5). #/misc/etc/auto.misc --timeout=60 #/misc/etc/auto.misc #/net /etc/auto.net /petunia /etc/petunia.misc --timeout=60 petunia.misc # # $Id: auto.misc,v 1.2 2003/09/29 08:22:35 raven Exp $ # # This is an automounter map and it has the following format # key [ -mount-options-separated-by-comma ] location # Details may be found in the autofs(5) manpage cd -fstype=iso9660,ro,nosuid,nodev :/dev/cdrom tony -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/tony chris -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/chris shared-fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/SharedDocs linuxbackups -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/linuxbackups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/40189/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 40189] Re: [SRU] [xenial] autofs needs to be restarted to pick up some shares
Today I've checked in Xenial with autofs 5.1.1-1ubuntu3.1. So far it seems to be working here as well. I would guess this bug is fixed then. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/40189 Title: [SRU] [xenial] autofs needs to be restarted to pick up some shares Status in autofs package in Ubuntu: Fix Released Status in autofs5 package in Ubuntu: Invalid Status in upstart package in Ubuntu: Invalid Status in autofs source package in Xenial: Incomplete Bug description: I am using autofs to access shares on a Windows XP machine from a Kubuntu AMD64 machine. The problems applies in both Breezy and Dapper. EDIT: confirmed with similar configuration on Intrepid with a NetApp filer hosting NFS. Server OS removed from summary. When I first try to access the mount point via cd or in Konqueror it does not exist. However, if I then restart autofs (/etc/init.d/autofs restart) everythin then works OK. My config files are: auto.master # # $Id: auto.master,v 1.3 2003/09/29 08:22:35 raven Exp $ # # Sample auto.master file # This is an automounter map and it has the following format # key [ -mount-options-separated-by-comma ] location # For details of the format look at autofs(5). #/misc/etc/auto.misc --timeout=60 #/misc/etc/auto.misc #/net /etc/auto.net /petunia /etc/petunia.misc --timeout=60 petunia.misc # # $Id: auto.misc,v 1.2 2003/09/29 08:22:35 raven Exp $ # # This is an automounter map and it has the following format # key [ -mount-options-separated-by-comma ] location # Details may be found in the autofs(5) manpage cd -fstype=iso9660,ro,nosuid,nodev :/dev/cdrom tony -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/tony chris -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/chris shared-fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/SharedDocs linuxbackups -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/linuxbackups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/40189/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1755138] [NEW] Update URL to project Homepage in package metadata
Public bug reported: Description:Ubuntu 16.04.4 LTS Release:16.04 logrotate: Installiert: 3.8.7-2ubuntu2.16.04.2 Installationskandidat: 3.8.7-2ubuntu2.16.04.2 The URL to the project Homepage is wrong: ~~~ Homepage: https://fedorahosted.org/logrotate/ ~~~ The URL leads to a page that informs you about the retirement of fedorahosted (see https://fedoraproject.org/wiki/Infrastructure /Fedorahosted-retirement). I think the correct URL should be https://github.com/logrotate/logrotate. This is only a minor flaw but still it would be nice if it gets fixed. ** Affects: logrotate (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1755138 Title: Update URL to project Homepage in package metadata Status in logrotate package in Ubuntu: New Bug description: Description: Ubuntu 16.04.4 LTS Release: 16.04 logrotate: Installiert: 3.8.7-2ubuntu2.16.04.2 Installationskandidat: 3.8.7-2ubuntu2.16.04.2 The URL to the project Homepage is wrong: ~~~ Homepage: https://fedorahosted.org/logrotate/ ~~~ The URL leads to a page that informs you about the retirement of fedorahosted (see https://fedoraproject.org/wiki/Infrastructure /Fedorahosted-retirement). I think the correct URL should be https://github.com/logrotate/logrotate. This is only a minor flaw but still it would be nice if it gets fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1755138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 40189] Re: [SRU] [xenial] autofs needs to be restarted to pick up some shares
Is there anything else to do? Any chance to get a version update in Xenial? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/40189 Title: [SRU] [xenial] autofs needs to be restarted to pick up some shares Status in autofs package in Ubuntu: Confirmed Status in autofs5 package in Ubuntu: Invalid Status in upstart package in Ubuntu: Invalid Bug description: I am using autofs to access shares on a Windows XP machine from a Kubuntu AMD64 machine. The problems applies in both Breezy and Dapper. EDIT: confirmed with similar configuration on Intrepid with a NetApp filer hosting NFS. Server OS removed from summary. When I first try to access the mount point via cd or in Konqueror it does not exist. However, if I then restart autofs (/etc/init.d/autofs restart) everythin then works OK. My config files are: auto.master # # $Id: auto.master,v 1.3 2003/09/29 08:22:35 raven Exp $ # # Sample auto.master file # This is an automounter map and it has the following format # key [ -mount-options-separated-by-comma ] location # For details of the format look at autofs(5). #/misc/etc/auto.misc --timeout=60 #/misc/etc/auto.misc #/net /etc/auto.net /petunia /etc/petunia.misc --timeout=60 petunia.misc # # $Id: auto.misc,v 1.2 2003/09/29 08:22:35 raven Exp $ # # This is an automounter map and it has the following format # key [ -mount-options-separated-by-comma ] location # Details may be found in the autofs(5) manpage cd -fstype=iso9660,ro,nosuid,nodev :/dev/cdrom tony -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/tony chris -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/chris shared-fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/SharedDocs linuxbackups -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/linuxbackups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/40189/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 40189] Re: [SRU] [xenial] autofs needs to be restarted to pick up some shares
I've just checked in Bionic: ~~~ $ uname -rvsop Linux 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Bionic Beaver (development branch) Release:18.04 Codename: bionic $ sudo apt list autofs Auflistung... Fertig autofs/bionic,now 5.1.2-1ubuntu2 amd64 [installiert] ~~~ In this version the bug seems to be fixed. AutoFS works as expected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/40189 Title: [SRU] [xenial] autofs needs to be restarted to pick up some shares Status in autofs package in Ubuntu: Confirmed Status in autofs5 package in Ubuntu: Invalid Status in upstart package in Ubuntu: Invalid Bug description: I am using autofs to access shares on a Windows XP machine from a Kubuntu AMD64 machine. The problems applies in both Breezy and Dapper. EDIT: confirmed with similar configuration on Intrepid with a NetApp filer hosting NFS. Server OS removed from summary. When I first try to access the mount point via cd or in Konqueror it does not exist. However, if I then restart autofs (/etc/init.d/autofs restart) everythin then works OK. My config files are: auto.master # # $Id: auto.master,v 1.3 2003/09/29 08:22:35 raven Exp $ # # Sample auto.master file # This is an automounter map and it has the following format # key [ -mount-options-separated-by-comma ] location # For details of the format look at autofs(5). #/misc/etc/auto.misc --timeout=60 #/misc/etc/auto.misc #/net /etc/auto.net /petunia /etc/petunia.misc --timeout=60 petunia.misc # # $Id: auto.misc,v 1.2 2003/09/29 08:22:35 raven Exp $ # # This is an automounter map and it has the following format # key [ -mount-options-separated-by-comma ] location # Details may be found in the autofs(5) manpage cd -fstype=iso9660,ro,nosuid,nodev :/dev/cdrom tony -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/tony chris -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/chris shared-fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/SharedDocs linuxbackups -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/linuxbackups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/40189/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1739247] [NEW] [software-version-update] OpenSSH 7.3 for Xenial Xerus
Public bug reported: Is it possible to update or rebase the openssh package in Xenial to at least version 7.3? Besides the bugfixes in this release I would like to use the ProxyJump option introduced in this version. See [OpenSSH 7.3]( https://www.openssh.com/txt/release-7.3) for further information. Since Xenial is supported until April 2021 I guess an update of OpenSSH would be nice. ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: upgrade-software-version ** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1739247 Title: [software-version-update] OpenSSH 7.3 for Xenial Xerus Status in openssh package in Ubuntu: New Bug description: Is it possible to update or rebase the openssh package in Xenial to at least version 7.3? Besides the bugfixes in this release I would like to use the ProxyJump option introduced in this version. See [OpenSSH 7.3]( https://www.openssh.com/txt/release-7.3) for further information. Since Xenial is supported until April 2021 I guess an update of OpenSSH would be nice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1739247/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 40189] Re: autofs needs to be restarted to pick up some shares
Would there be an updated version in the next xenial point release? Is there any chance to get autofs (5.1.2-1) at all? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/40189 Title: autofs needs to be restarted to pick up some shares Status in autofs package in Ubuntu: Confirmed Status in autofs5 package in Ubuntu: Invalid Status in upstart package in Ubuntu: Invalid Bug description: I am using autofs to access shares on a Windows XP machine from a Kubuntu AMD64 machine. The problems applies in both Breezy and Dapper. EDIT: confirmed with similar configuration on Intrepid with a NetApp filer hosting NFS. Server OS removed from summary. When I first try to access the mount point via cd or in Konqueror it does not exist. However, if I then restart autofs (/etc/init.d/autofs restart) everythin then works OK. My config files are: auto.master # # $Id: auto.master,v 1.3 2003/09/29 08:22:35 raven Exp $ # # Sample auto.master file # This is an automounter map and it has the following format # key [ -mount-options-separated-by-comma ] location # For details of the format look at autofs(5). #/misc/etc/auto.misc --timeout=60 #/misc/etc/auto.misc #/net /etc/auto.net /petunia /etc/petunia.misc --timeout=60 petunia.misc # # $Id: auto.misc,v 1.2 2003/09/29 08:22:35 raven Exp $ # # This is an automounter map and it has the following format # key [ -mount-options-separated-by-comma ] location # Details may be found in the autofs(5) manpage cd -fstype=iso9660,ro,nosuid,nodev :/dev/cdrom tony -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/tony chris -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/chris shared-fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/SharedDocs linuxbackups -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/linuxbackups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/40189/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 40189] Re: autofs needs to be restarted to pick up some shares
I was able to reproduce the issue on a fresh install of Xenial today. You could find the degug log at: https://paste.ubuntuusers.de/423433/ ** Changed in: autofs (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/40189 Title: autofs needs to be restarted to pick up some shares Status in autofs package in Ubuntu: New Status in autofs5 package in Ubuntu: Invalid Status in upstart package in Ubuntu: Invalid Bug description: I am using autofs to access shares on a Windows XP machine from a Kubuntu AMD64 machine. The problems applies in both Breezy and Dapper. EDIT: confirmed with similar configuration on Intrepid with a NetApp filer hosting NFS. Server OS removed from summary. When I first try to access the mount point via cd or in Konqueror it does not exist. However, if I then restart autofs (/etc/init.d/autofs restart) everythin then works OK. My config files are: auto.master # # $Id: auto.master,v 1.3 2003/09/29 08:22:35 raven Exp $ # # Sample auto.master file # This is an automounter map and it has the following format # key [ -mount-options-separated-by-comma ] location # For details of the format look at autofs(5). #/misc/etc/auto.misc --timeout=60 #/misc/etc/auto.misc #/net /etc/auto.net /petunia /etc/petunia.misc --timeout=60 petunia.misc # # $Id: auto.misc,v 1.2 2003/09/29 08:22:35 raven Exp $ # # This is an automounter map and it has the following format # key [ -mount-options-separated-by-comma ] location # Details may be found in the autofs(5) manpage cd -fstype=iso9660,ro,nosuid,nodev :/dev/cdrom tony -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/tony chris -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/chris shared-fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/SharedDocs linuxbackups -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/linuxbackups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/40189/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 40189] Re: autofs needs to be restarted to pick up some shares
Good evening,
I see this bug in Ubuntu 16.04.1 LTS with autofs version 5.1.1-1ubuntu3
when I try to access cifs shares from my NAS.
When I try to access the shares with 'cd' or 'ls' after boot with
network on both sides up and running I got the error message: "File or
Directory not found." After running `sudo systemctl restart
autofs.service` it works like a charme.
Here is my '''/etc/auto.master.d/diskstation.autofs''':
~~~
/home/tronde/diskstation /etc/auto.diskstation
~~~
And my '''/etc/auto.diskstation''':
~~~
music -fstype=cifs,uid=1000,credentials=/home/tronde/.smbcredentials
://IP-ADRESSE/music
photo -fstype=cifs,uid=1000,credentials=/home/tronde/.smbcredentials
://IP-ADRESSE/photo
share -fstype=cifs,uid=1000,credentials=/home/tronde/.smbcredentials
://IP-ADRESSE/share
video -fstype=cifs,uid=1000,credentials=/home/tronde/.smbcredentials
://IP-ADRESSE/video
home -fstype=cifs,uid=1000,gid=1000,credentials=/home/tronde/.smbcredentials
://IP-ADRESSE/home
~~~
The service configuration looks like:
~~~
cat /run/systemd/generator.late/graphical.target.wants/autofs.service
# Automatically generated by systemd-sysv-generator
[Unit]
Documentation=man:systemd-sysv-generator(8)
SourcePath=/etc/init.d/autofs
Description=LSB: Automounts filesystems on demand
Before=multi-user.target
Before=multi-user.target
Before=multi-user.target
Before=graphical.target
Before=shutdown.target
After=network-online.target
After=remote-fs.target
After=systemd-journald-dev-log.socket
After=ypbind.service
After=nslcd.service
After=slapd.service
Wants=network-online.target
Conflicts=shutdown.target
[Service]
Type=forking
Restart=no
TimeoutSec=5min
IgnoreSIGPIPE=no
KillMode=process
GuessMainPID=no
RemainAfterExit=yes
ExecStart=/etc/init.d/autofs start
ExecStop=/etc/init.d/autofs stop
ExecReload=/etc/init.d/autofs reload
~~~
The source of this configuration from '''/etc/init.d/autofs''':
~~~
cat /etc/init.d/autofs
#! /bin/sh
#
### BEGIN INIT INFO
# Provides: autofs
# Required-Start: $network $remote_fs $syslog
# Required-Stop: $network $remote_fs $syslog
# Should-Start: ypbind nslcd slapd
# Should-Stop: ypbind nslcd slapd
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Automounts filesystems on demand
# Description: Automounts filesystems on demand
### END INIT INFO
# Location of the automount daemon and the init directory
#
PROG=automount
DAEMON=/usr/sbin/$PROG
NAME=autofs
PIDFILE="/var/run/$NAME.pid"
test -e $DAEMON || exit 0
PATH=/sbin:/usr/sbin:/bin:/usr/bin
export PATH
. /lib/lsb/init-functions
#
# load customized configuation settings
#
if [ -r /etc/default/autofs ]; then
. /etc/default/autofs
fi
start_stop_autofs() {
start-stop-daemon "$@" --pidfile $PIDFILE --exec $DAEMON -- \
$OPTIONS --pid-file $PIDFILE
}
start() {
log_action_begin_msg "Starting $PROG"
if ! grep -qw autofs /proc/filesystems
then
if ! modprobe autofs4 >/dev/null 2>&1
then
log_action_end_msg 1 "failed to load autofs4 module"
return 1
fi
elif [ -f /proc/modules ] && grep -q "^autofs[^4]" /proc/modules
then
log_action_end_msg 1 "autofs kernel module is loaded, autofs4
required"
return 1
fi
if ! start_stop_autofs --start --oknodo --quiet ; then
log_action_end_msg 1 "no valid automount entries defined."
return 1
fi
log_end_msg 0
return 0
}
stop() {
log_action_begin_msg "Stopping $PROG"
if ! start_stop_autofs --stop --retry 5 --oknodo --quiet ; then
log_action_end_msg 1
return 1
fi
log_end_msg 0
return 0
}
reload() {
log_action_begin_msg "Reloading $PROG maps"
if ! start_stop_autofs --stop --signal=HUP --quiet
then
log_action_end_msg 1 "$PROG not running"
return 1
fi
log_action_end_msg 0
return 0
}
forcestart() {
OPTIONS="$OPTIONS --force"
start
}
case "$1" in
start|forcestart|stop|reload)
$1
;;
restart|force-reload)
stop
start
;;
forcerestart)
stop
forcestart
;;
status)
status_of_proc -p $PIDFILE $DAEMON $PROG
;;
*)
echo "Usage: $0
{start|forcestart|stop|restart|forcerestart|reload|force-reload|status}"
exit 1
;;
esac
~~~
This way autofs has no advantage over the manual mount with mount.cifs.
Open this bug and fix ist, please.
Best regards,
Tronde
--
You received this bug notificat
