Re: Sid: NFS after upgrade [solved] please fix /etc/init.d/rpcbind
On 2018-10-28 16:58 +, Grzesiek Sójka wrote: > On 10/28/18 2:10 PM, Sven Joachim wrote: >> Wouldn't it be better to fix the init system that sets such a bad >> default PATH? Whatever init system that may be - sysv-rc's >> /etc/init.d/rc script sets PATH=/sbin:/usr/sbin:/bin:/usr/bin, so this >> should not happen with sysvinit + sysv-rc. > > Please, keep in mind that /etc/init.d/rpcbind may also be invoked by > /etc/network/if-up.d/mountnfs (after bringing up interfaces): > > # grep PATH /etc/network/if-up.d/mountnfs > PATH=/sbin:/bin I see. This could be fixed in ifupdown by not setting PATH in its init scripts or by setting PATH in the rpcbind init script. Overall PATH handling in init scripts is a total mess and needs to be cleaned up. These days /usr is supposed to be mounted by the initramfs if it's on a different filesystem than /, so init scripts can rely on it being present. Please file a bug - most maintainers use systemd these days where those problems do not exist, so they won't notice them. Cheers, Sven
Re: Sid: NFS after upgrade [solved] please fix /etc/init.d/rpcbind
On 10/28/18 2:10 PM, Sven Joachim wrote: Wouldn't it be better to fix the init system that sets such a bad default PATH? Whatever init system that may be - sysv-rc's /etc/init.d/rc script sets PATH=/sbin:/usr/sbin:/bin:/usr/bin, so this should not happen with sysvinit + sysv-rc. Please, keep in mind that /etc/init.d/rpcbind may also be invoked by /etc/network/if-up.d/mountnfs (after bringing up interfaces): # grep PATH /etc/network/if-up.d/mountnfs PATH=/sbin:/bin What init system do you use? # apt --installed list | grep sys | cut -f 1 -d ' ' busybox-syslogd/unstable,now init-system-helpers/unstable,now libboost-filesystem1.62.0/unstable,now libboost-system1.62.0/unstable,now libsystemd0/unstable,now sysv-rc/unstable,now sysvinit-core/unstable,now sysvinit-utils/unstable,now -- Pozdrawiam Grzesiek Wysłane z kompa wolnego od wirusów Billa Gatesa.
Re: Sid: NFS after upgrade [solved] please fix /etc/init.d/rpcbind
On 2018-10-28 14:47 +, Grzesiek Sójka wrote: > On 10/28/18 11:27 AM, Grzesiek Sójka wrote: >> Hi there, >> >> I just upgraded Sid and now I get the following during boot: >> >> [] Configuring network interfaces.../etc/init.d/rpcbind: 42: >> /etc/init.d/rpcbind: stat: not found >> /run/rpcbind not owned by root failed! >> Starting NFS common utilities: statd >> Not starting: portmapper is not running ... (warning). >> mount.nfs: rpc.statd is not running but is required for remote locking. >> mount.nfs: Either use '-o nolock' to keep locks local, or start statd. >> mount.nfs: rpc.statd is not running but is required for remote locking. >> mount.nfs: Either use '-o nolock' to keep locks local, or start statd. >> done. >> [ ok ] Starting RPC port mapper daemon: rpcbind. >> [ ok ] Starting NFS common utilities: statd. > > The problem is caused by wrong setting of the PATH variable during the > execution of the /etc/init.d/rpcbind script. The new version uses stat > binary which is located in /usr/bin but the PATH is set to > PATH='/sbin:/bin'. This leaves the question why PATH is set that way. > As a workaround I added PATH="$PATH:/usr/bin" to > /etc/init.d/rpcbind. It works fine now. > > Please fix init scripts. Wouldn't it be better to fix the init system that sets such a bad default PATH? Whatever init system that may be - sysv-rc's /etc/init.d/rc script sets PATH=/sbin:/usr/sbin:/bin:/usr/bin, so this should not happen with sysvinit + sysv-rc. What init system do you use? Cheers, Sven
Re: Sid: NFS after upgrade [solved] please fix /etc/init.d/rpcbind
On 10/28/18 11:27 AM, Grzesiek Sójka wrote: Hi there, I just upgraded Sid and now I get the following during boot: [] Configuring network interfaces.../etc/init.d/rpcbind: 42: /etc/init.d/rpcbind: stat: not found /run/rpcbind not owned by root failed! Starting NFS common utilities: statd Not starting: portmapper is not running ... (warning). mount.nfs: rpc.statd is not running but is required for remote locking. mount.nfs: Either use '-o nolock' to keep locks local, or start statd. mount.nfs: rpc.statd is not running but is required for remote locking. mount.nfs: Either use '-o nolock' to keep locks local, or start statd. done. [ ok ] Starting RPC port mapper daemon: rpcbind. [ ok ] Starting NFS common utilities: statd. The problem is caused by wrong setting of the PATH variable during the execution of the /etc/init.d/rpcbind script. The new version uses stat binary which is located in /usr/bin but the PATH is set to PATH='/sbin:/bin'. As a workaround I added PATH="$PATH:/usr/bin" to /etc/init.d/rpcbind. It works fine now. Please fix init scripts. -- Pozdrawiam Grzesiek Wysłane z kompa wolnego od wirusów Billa Gatesa.
