Txwikinger is right in its explanations of my intentions for this bug report, it is for consistency with all others usages of hwclock command in the script (I'm sorry, I should have explain that in my report). It's not critical, and again less critical in this case because the flag is "--adjust" which not involve an important operation contrary to actions involved by "--set" or "--hctosys" flags. I guessed that if the complete path was given for hwclock it was a precaution, and if developer of this script made this choice it may have a good raison to do that. Normally, it can perfectly function without full path, but for the full path suppression suggested by Matt, maybe we should ensure that the choice of using full path had no particular goal which may a precaution policy (to not rely on PATH variable value for example).
Making search about that, I tried to consult the documentation file indicated in this script comments, and I noticed that the filename was not complete because of a missing extension (see bug #104467 for details). -- [hwclock] full path for a command possibly uncommented in init script https://bugs.launchpad.net/bugs/103680 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
