| View previous topic :: View next topic |
| Author |
Message |
Xywa
Veteran
Joined: 23 Jul 2005
Posts: 1631
Location: /mnt/Gentoo/Europe
|
 Posted: Wed May 25, 2016 9:44 am Post subject: please convert to openrc-run |
 |
|
Hi,
During system start after a boot, I could see for few packages such messages: please convert to openrc-run
Unfortunately, I cannot find those messages in any logs, but I can make a photo if needed. |
|
| Back to top |
|
 |
bstaletic
Apprentice
Joined: 05 Apr 2014
Posts: 253
|
| Posted: Wed May 25, 2016 9:59 am Post subject: |
|
|
No need for you to do anythibg on your pc. OpenRC previously used "#!/sbin/runscript" and recently switched to "#!/sbin/openrc-run" while deprecating the former. It should bea developers' task to switch to the new bang (is that the right term?). All you can do is report the scripts producing the warnings to the bugtracker, butI assume the developersare aware of these.
If the warnings do irritate you, you could change those yourself. You'd have to do that on every OpenRC upgrade. |
|
| Back to top |
|
|
khayyam
Watchman
Joined: 07 Jun 2012
Posts: 6227
Location: Room 101
|
| Posted: Wed May 25, 2016 11:36 am Post subject: |
|
|
Xywa, bstaletic ... this again.
We can assume that it wasn't the user who inserted such a warning so they can be forgiven for taking such instructions for something *they* are being asked to do.
As for the switch to openrc-run, no one should be under the illusion that this is anything but a case in which the openrc developers have created a disproportionate level of disruption, confusion, work, etc, to fix something which was at best a corner case.
best ... khay |
|
| Back to top |
|
|
bstaletic
Apprentice
Joined: 05 Apr 2014
Posts: 253
|
| Posted: Wed May 25, 2016 1:04 pm Post subject: |
|
|
Khay,
Where can I read about the reasoning behind the runscript->openrc-run change? I'm fairly new to Gentoo and do not remember openrc before the switch.
Thanks |
|
| Back to top |
|
|
khayyam
Watchman
Joined: 07 Jun 2012
Posts: 6227
Location: Room 101
|
| Posted: Wed May 25, 2016 1:19 pm Post subject: |
|
|
| bstaletic wrote: | | Where can I read about the reasoning behind the runscript->openrc-run change? I'm fairly new to Gentoo and do not remember openrc before the switch. |
bstaletic ... you can find the details/comments in bug 494220, and the forum thread from 2014 runscript is deprecated; please use openrc-run instead.
best ... khay |
|
| Back to top |
|
|
proteusx
Guru
Joined: 21 Jan 2008
Posts: 338
|
| Posted: Wed May 25, 2016 2:48 pm Post subject: |
|
|
It would be nice if the warning messages were prepended with the word: Maintainers.
Anyway the solution is simple:
| Code: | | find /etc/init.d -type f -exec sed -i 's/runscript/openrc-run/' {} + |
|
|
| Back to top |
|
|
Tony0945
Watchman
Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA
|
| Posted: Wed May 25, 2016 3:12 pm Post subject: |
|
|
WOW! There must be far more openrc users than minicom users, why didn't minicom change? Or the ebuild Dependency have !minicom added?
VT100 terminals! What a blast from the past! Thirty years ago? |
|
| Back to top |
|
|
freke
l33t
Joined: 23 Jan 2003
Posts: 977
Location: Somewhere in Denmark
|
| Posted: Wed May 25, 2016 3:51 pm Post subject: |
|
|
Booting on a headless device I wasn't aware of this as it doesn't seems to get logged in rc.log?
Checking my /etc/init.d I see approx. 50% of the scripts uses runscript the other 50% uses openrc-run.
Should bugs be filed for these (if there's not already)? |
|
| Back to top |
|
|
khayyam
Watchman
Joined: 07 Jun 2012
Posts: 6227
Location: Room 101
|
| Posted: Wed May 25, 2016 4:49 pm Post subject: |
|
|
| Tony0945 wrote: |
WOW! There must be far more openrc users than minicom users, why didn't minicom change? Or the ebuild Dependency have !minicom added? |
Tony ... yes, you'd expect that the package effecting the least disturbance would be changed, but that isn't what such a change is about. The executables don't share the same path, and there are no reported bugs due to minicom also having a runscript, it was done as debian developers requested it (debian maintains minicom). The developers were more interested in ingratiating themselves with debian/minicom's upstream than in doing the right thing for their distribution/users.
This is all in direct violation of our charter, but la-la-la, nothing to see here.
| Tony0945 wrote: | | VT100 terminals! What a blast from the past! Thirty years ago? |
Yes, but they are still used for serial lines.
| freke wrote: | | Should bugs be filed for these (if there's not already)? |
Personally I'm not going to help out when developers make such stupid, idiotic, changes, and then when the effect of such changes becomes apparent pretend that it isn't stupid and idiotic and that they are doing work.
best ... khay |
|
| Back to top |
|
|
proteusx
Guru
Joined: 21 Jan 2008
Posts: 338
|
| Posted: Wed May 25, 2016 5:34 pm Post subject: |
|
|
| khayyam wrote: | | ...make such stupid, idiotic, changes, and then when the effect of such changes becomes apparent pretend that it isn't stupid and idiotic and that they are doing work. |
The all too common malaise of our time, alas. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54236
Location: 56N 3W
|
| Posted: Wed May 25, 2016 7:30 pm Post subject: |
|
|
Tony0945,
I use OpenRC (pre change) and minicom together. They don't seem to get their runscripts confused.
It only seems to be a problem on Debian ... but but Debian switched to systemd, so they wont be using OpenRC any time soon.
They fixed it for themselves.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
Tony0945
Watchman
Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA
|
| Posted: Wed May 25, 2016 8:04 pm Post subject: |
|
|
| Unbelievable! (but I do believe it) |
|
| Back to top |
|
|
Ant P.
Watchman
Joined: 18 Apr 2009
Posts: 6920
|
| Posted: Wed May 25, 2016 10:04 pm Post subject: |
|
|
| Yep, it's almost as if separate /sbin and /usr/bin exists for precisely this reason of avoiding file collisions between system and user tools, isn't it... |
|
| Back to top |
|
|
Tony0945
Watchman
Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA
|
| Posted: Wed May 25, 2016 10:40 pm Post subject: |
|
|
| Ant P. wrote: | | Yep, it's almost as if separate /sbin and /usr/bin exists for precisely this reason of avoiding file collisions between system and user tools, isn't it... |
I seem to remember a proposal to symlink them all together. |
|
| Back to top |
|
|
bstaletic
Apprentice
Joined: 05 Apr 2014
Posts: 253
|
| Posted: Wed May 25, 2016 10:48 pm Post subject: |
|
|
| Ant P. wrote: | | Yep, it's almost as if separate /sbin and /usr/bin exists for precisely this reason of avoiding file collisions between system and user tools, isn't it... |
Aren't we using /{,usr}/{,s}bin as a symlink to /usr/bin?? So what's this "separate /sbin and /usr/bin" you're talking about? [/sarcasm] |
|
| Back to top |
|
|
Xywa
Veteran
Joined: 23 Jul 2005
Posts: 1631
Location: /mnt/Gentoo/Europe
|
| Posted: Thu May 26, 2016 7:31 am Post subject: |
|
|
Hi,
So what should I do to move from runscript into openrc-run? |
|
| Back to top |
|
|
Syl20
l33t
Joined: 04 Aug 2005
Posts: 619
Location: France
|
| Posted: Thu May 26, 2016 10:21 am Post subject: |
|
|
| Code: | | # grep '^#!/sbin/runscript' /etc/init.d/* |
If you really want to convert all the scripts, in one command (but, of course, make backups first) :
| Code: | | # sed -i 's_#!/sbin/runscript_#!/sbin/openrc-run_' /etc/init.d/* |
That said, I have a lot more startup scripts containing the #!/sbin/runscript shebang than the #!/sbin/openrc-run one. And I encouter no problem at all.
Moreover, both /sbin/runscript and /sbin/openrc-run files are symlinks to /sbin/openrc (openrc version 0.19.1). |
|
| Back to top |
|
|
proteusx
Guru
Joined: 21 Jan 2008
Posts: 338
|
| Posted: Thu May 26, 2016 10:58 am Post subject: |
|
|
| Syl20 wrote: | If you really want to convert all the scripts, in one command (but, of course, make backups first) :
| Code: | | # sed -i 's_#!/sbin/runscript_#!/sbin/openrc-run_' /etc/init.d/* |
|
Do it this way and you will certainly bugger the symlinks to net.lo.
The problem is with openrc-021 where some bright spark decided in his wisdom to "Make the warnings more visible"
thus polluting our start up screens with irksome warnings that in reality concern only the maintainers. |
|
| Back to top |
|
|
Xywa
Veteran
Joined: 23 Jul 2005
Posts: 1631
Location: /mnt/Gentoo/Europe
|
| Posted: Thu May 26, 2016 1:06 pm Post subject: |
|
|
| Code: | # grep '^#!/sbin/runscript' /etc/init.d/*
/etc/init.d/alsasound:#!/sbin/runscript
/etc/init.d/bluetooth:#!/sbin/runscript
/etc/init.d/busybox-ntpd:#!/sbin/runscript
/etc/init.d/busybox-watchdog:#!/sbin/runscript
/etc/init.d/consolekit:#!/sbin/runscript
/etc/init.d/dhcpd:#!/sbin/runscript
/etc/init.d/dhcrelay:#!/sbin/runscript
/etc/init.d/dhcrelay6:#!/sbin/runscript
/etc/init.d/fancontrol:#!/sbin/runscript
/etc/init.d/fuse:#!/sbin/runscript
/etc/init.d/gpm:#!/sbin/runscript
/etc/init.d/hdparm:#!/sbin/runscript
/etc/init.d/ip6tables:#!/sbin/runscript
/etc/init.d/iptables:#!/sbin/runscript
/etc/init.d/kmod-static-nodes:#!/sbin/runscript
/etc/init.d/laptop_mode:#!/sbin/runscript
/etc/init.d/lm_sensors:#!/sbin/runscript
/etc/init.d/mysql:#!/sbin/runscript
/etc/init.d/net.lo:#!/sbin/runscript
/etc/init.d/NetworkManager:#!/sbin/runscript
/etc/init.d/nvidia-persistenced:#!/sbin/runscript
/etc/init.d/nvidia-smi:#!/sbin/runscript
/etc/init.d/pwcheck:#!/sbin/runscript
/etc/init.d/pydoc-2.7:#!/sbin/runscript
/etc/init.d/pydoc-3.4:#!/sbin/runscript
/etc/init.d/pydoc-3.5:#!/sbin/runscript
/etc/init.d/rfcomm:#!/sbin/runscript
/etc/init.d/rsyncd:#!/sbin/runscript
/etc/init.d/saslauthd:#!/sbin/runscript
/etc/init.d/sshd:#!/sbin/runscript
/etc/init.d/syslog-ng:#!/sbin/runscript
/etc/init.d/udev:#!/sbin/runscript
/etc/init.d/vixie-cron:#!/sbin/runscript
/etc/init.d/wicd:#!/sbin/runscript
/etc/init.d/wpa_supplicant:#!/sbin/runscript
/etc/init.d/xdm:#!/sbin/runscript
/etc/init.d/xdm-setup:#!/sbin/runscript |
So now should I do this?
| Code: | | # sed -i 's_#!/sbin/runscript_#!/sbin/openrc-run_' /etc/init.d/* |
What should I back up? |
|
| Back to top |
|
|
khayyam
Watchman
Joined: 07 Jun 2012
Posts: 6227
Location: Room 101
|
| Posted: Thu May 26, 2016 1:30 pm Post subject: |
|
|
| Xywa wrote: | So now should I do this?
| Code: | | # sed -i 's_#!/sbin/runscript_#!/sbin/openrc-run_' /etc/init.d/* |
|
Xywa ... I would use the following:
| Code: | | # sed -i -- '1s/runscript/openrc-run/' /etc/init.d/*(.) |
... but that is using zsh's "glob qualifiers", so you can omit that if using bash:
| Code: | | # sed -i -- '1s/runscript/openrc-run/' /etc/init.d/* |
| Xywa wrote: | | What should I back up? |
You can make a copy of /etc/init.d before hand, or provide a suffix to sed's '-i', eg:
| Code: | | # sed -i.bak -- '1s/runscript/openrc-run/' /etc/init.d/* |
best ... khay |
|
| Back to top |
|
|
proteusx
Guru
Joined: 21 Jan 2008
Posts: 338
|
| Posted: Thu May 26, 2016 2:40 pm Post subject: |
|
|
| Code: | --- openrc-0.21/src/rc/openrc-run.c 2016-05-24 22:02:35.000000000 +0300
+++ openrc-0.21/src/rc/openrc-run.new.c 2016-05-26 17:20:47.421229738 +0300
@@ -1173,8 +1173,8 @@
if (argc < 3)
usage(EXIT_FAILURE);
- if (runscript)
- ewarn("%s uses runscript, please convert to openrc-run.", service);
+ /* if (runscript) */
+ /* ewarn("%s uses runscript, please convert to openrc-run.", service); */
/* Change dir to / to ensure all init scripts don't use stuff in pwd */
if (chdir("/") == -1) |
Put the above patch in | Code: | | /usr/portage/patches/sys-apps/open-rc/silence-irksome-warnings.patch |
then rebuild openrc and you will silence him in perpetuity.
That is why we love Gentoo! |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54236
Location: 56N 3W
|
| Posted: Thu May 26, 2016 6:28 pm Post subject: |
|
|
proteusx,
I like that patch :)
In the light of some dubious design decisions make in more recent versions of openrc, I have >= 0.18 hard masked.
Other correspondents in this thread are sticking with even earlier versions.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
khayyam
Watchman
Joined: 07 Jun 2012
Posts: 6227
Location: Room 101
|
| Posted: Thu May 26, 2016 8:01 pm Post subject: |
|
|
| NeddySeagoon wrote: | | Other correspondents in this thread are sticking with even earlier versions. |
Neddy ... in my case that would be =sys-apps/openrc-0.12.4. Given that I've already had one 'openrc-run' initscript dropped on me without so much as a .cfg_xxxx I will probably me migrating to something other than openrc in the not too distant future. I'm also in the market for a linux kernel[1] that doesn't lock my machine up on a weekly basis, so if you hear of anything let me know ;)
best ... khay
1) The last non-crashing kernel I've had was 3.13.11 and I can't keep track of the various kernels I've built (or attempted to build) in the past year or more. I just had a hard lock up with 3.12.58, no backtrace, or any idea what caused it ... linux is looking more and more like a pile of crud. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54236
Location: 56N 3W
|
| Posted: Thu May 26, 2016 8:21 pm Post subject: |
|
|
khayyam,
That sounds like hardware or a very special condition that only hurts a small number of users.
How marginal is the PSU?
lm-sensors and friends won't provide useful information. Its the 12v transient response that matters.
Think of the CPU going from almost zero to 120w in a fraction of a nanosecond.
Have a look at the Vcore power connector, that's the extra 12v supply to the motherboard, mine is quite charred.
It runs for about 6 months, then needs a good 'waggle' to clean the mating surfaces and its good for another six months.
In theory, its all fine but its transient conditions that make it fail.
Another random lockups favourite is the Vcore capacitors close to the CPU. They get a very hard life and are in a hot location too.
Its got much harder to spot failures by eye now that they they are not tubular electrolytics any more.
I suspect that kernel 3.13.11 does not push your hardware as hard as newer kernels, so you don't see PSU transient issues.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
Tony0945
Watchman
Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA
|
| Posted: Thu May 26, 2016 9:28 pm Post subject: |
|
|
NeddySeagoon, you are on to something with the capacitors. Electrolytic capacitors cause an enormous amount of problems with electronic equipment especially after a Chinese spy sent the wrong formula from Japan. That's why I stick with Gigabyte mobos, for the extra copper and all Japanese capacitors.
Khay, what is your mobo and PSU make and model. PSU's can have bad caps too. It's important to not regularly tax the PSU over 50% of it's 12v rating.
You have helped me with so many software issues. I would love to help you with your hardware. I'd come over but I think you're thousands of miles from Chicago.
I've got 4.6.0 running on nine year old hardware from March 2007 and May 2007. If it's the kernel, then it's a configuration problem. The "newer" one is my server that's always on. I'm thinking of replacing it but only for speed. |
|
| Back to top |
|
|
|
Portage & Programming
