[yast-devel] Just note about PATH in YaPI modules
![](https://seccdn.libravatar.org/avatar/f9a9cf77af20d925b328ee8c95c0068c.jpg?s=120&d=mm&r=g)
I now find where is problem in NTP synchronization in RC3. It is problem that PATH in YaPI modules is not same as PATH for user root. So if you run any script or program from /usr/sbin or /sbin use full path to that script otherwise it is not found. Also I found that many YaPI modules doesn't log anything. Maybe it should be useful to add some logging to easier debugging customer issues. Thanks for attention Josef -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, webyast (language,time,basesystem,ntp) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/d18d0fd84170a8255c30388a800b96c8.jpg?s=120&d=mm&r=g)
* Josef Reidinger <jreidinger@suse.cz> [Nov 19. 2009 14:57]:
I now find where is problem in NTP synchronization in RC3. It is problem that PATH in YaPI modules is not same as PATH for user root.
Josef, thanks for finding this.
So if you run any script or program from /usr/sbin or /sbin use full path to that script otherwise it is not found.
Actually, this is a rule in YCP and the scr execute component will log a warning if commands don't specify the full path.
Also I found that many YaPI modules doesn't log anything. Maybe it should be useful to add some logging to easier debugging customer issues.
Please open a bug for this, so we can work on it later. Klaus --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/654c5b4f0d657240edff9440a901839b.jpg?s=120&d=mm&r=g)
On 19.11.2009 15:00, Klaus Kaempf wrote:
* Josef Reidinger <jreidinger@suse.cz> [Nov 19. 2009 14:57]: Actually, this is a rule in YCP and the scr execute component will log a warning if commands don't specify the full path.
That's nice, but it cannot help if you use another way to start a process (like `` operator in perl in this case).
Also I found that many YaPI modules doesn't log anything. Maybe it should be useful to add some logging to easier debugging customer issues.
The YaST DBus service logs input parameters and result for each call so at least some hints can be found there. But I agree this might not be sufficient in many cases. -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak@suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/c6230e4ce683f6f38991d06b0df892bc.jpg?s=120&d=mm&r=g)
On Thursday 19 of November 2009 15:49:57 Ladislav Slezak wrote:
On 19.11.2009 15:00, Klaus Kaempf wrote:
* Josef Reidinger <jreidinger@suse.cz> [Nov 19. 2009 14:57]: Actually, this is a rule in YCP and the scr execute component will log a warning if commands don't specify the full path.
That's nice, but it cannot help if you use another way to start a process (like `` operator in perl in this case).
Hm, maybe NTP.pm should touch the system using SCR, like other YaST modules. Mostly because of consistency, because in this case we know it is already running on target machine... j -- Jiri Suchomel SUSE LINUX, s.r.o. e-mail: jsuchome@suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Praha 9, Czech Republic http://www.suse.cz -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/f9a9cf77af20d925b328ee8c95c0068c.jpg?s=120&d=mm&r=g)
Jiří Suchomel write:
On Thursday 19 of November 2009 15:49:57 Ladislav Slezak wrote:
On 19.11.2009 15:00, Klaus Kaempf wrote:
* Josef Reidinger <jreidinger@suse.cz> [Nov 19. 2009 14:57]: Actually, this is a rule in YCP and the scr execute component will log a warning if commands don't specify the full path.
That's nice, but it cannot help if you use another way to start a process (like `` operator in perl in this case).
Hm, maybe NTP.pm should touch the system using SCR, like other YaST modules. Mostly because of consistency, because in this case we know it is already running on target machine...
j
Maybe, but I must check also performance because I sometime have problem with ntp communication timeout and another potential slow down could be bad. Also in perl is easier and more direct way to use `` then scr ;) -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, webyast (language,time,basesystem,ntp) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
participants (4)
-
Jiří Suchomel
-
Josef Reidinger
-
Klaus Kaempf
-
Ladislav Slezak