Re: cpupower

2018-06-24 Thread stan 
On Sun, 24 Jun 2018 21:26:04 -0700
Joe Zeff  wrote:

> On 06/24/2018 09:13 PM, Doug wrote:
> > What makes you folks think that a computer will run faster in a 
> > refrigerated environment?  Only if it was too hot to begin with
> > should it make any difference.  
> 
> Remember, this thread started out talking about working around a CPU 
> overheating.

Because of Tim's comment, I did a search for any info on this, and
found this video on youtube that addresses exactly this question:

https://www.youtube.com/watch?v=B8bhGw4vUFE

No cigar, the fridge just isn't designed to dissipate that kind of heat
on a continuous basis.  Saved me the time, money, and effort. :-)
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/PLQ4VNYU7OAWN4VZKH55EJV3GGRVC4HI/

Re: cpupower

2018-06-24 Thread Joe Zeff 

On 06/24/2018 09:13 PM, Doug wrote:
What makes you folks think that a computer will run faster in a 
refrigerated environment?  Only if it was too hot to begin with should 
it make any difference.


Remember, this thread started out talking about working around a CPU 
overheating.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/ILSXPDWPAADJ6PNMHZSDFJXTGCERUUFM/

Re: cpupower

2018-06-24 Thread Doug 


On 06/24/2018 11:10 PM, stan wrote:

On Mon, 25 Jun 2018 09:45:27 +0930
Tim via users  wrote:


Allegedly, on or about 24 June 2018, stan sent:

I've thought about buying one of those little fridges and putting
the system in it.

I remember seeing a page or two about people doing that, many years
ago.  Though I can't recall what their success was like.

I'd be concerned about moisture/condensation.

I'll have to look for those pages.  I think condensation isn't an issue
because there would be nothing to give off moisture, and the cool dry
air is dehydrating.  Leave a carrot out in the fridge for a few days
without any wrapping and it will start to become dried vegetable.  The
condensation occurs because of warming and cooling when vegetables are
wrapped in plastic.  The vegetables give up their moisture, and the
plastic is cooler than the vegetables because the fridge is blowing
cold air over it, so the water condenses.
___

What makes you folks think that a computer will run faster in a 
refrigerated environment?  Only if it was too hot to begin with should 
it make any difference.
You see monstrous warehouses of Bitcoin computers, and humungous fans 
and air conditioning systems on TV, but you are probably not running a 
computer
under those conditions. In reality, those computers would probably not 
run at all due to overheating in a hot closed environment and 
insufficient cooling.

--doug
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/R56VR27TYJBEU23IL3FKCLKZQ6SJK4H4/

Re: cpupower

2018-06-24 Thread stan 
On Mon, 25 Jun 2018 09:45:27 +0930
Tim via users  wrote:

> Allegedly, on or about 24 June 2018, stan sent:
> > I've thought about buying one of those little fridges and putting
> > the system in it.  
> 
> I remember seeing a page or two about people doing that, many years
> ago.  Though I can't recall what their success was like.
> 
> I'd be concerned about moisture/condensation.

I'll have to look for those pages.  I think condensation isn't an issue
because there would be nothing to give off moisture, and the cool dry
air is dehydrating.  Leave a carrot out in the fridge for a few days
without any wrapping and it will start to become dried vegetable.  The
condensation occurs because of warming and cooling when vegetables are
wrapped in plastic.  The vegetables give up their moisture, and the
plastic is cooler than the vegetables because the fridge is blowing
cold air over it, so the water condenses.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/MO53VRRX7EUNWCABCCRZ55WGOTAAHC37/

Re: cpupower

2018-06-24 Thread Joe Zeff 

On 06/24/2018 06:36 PM, Ed Greshko wrote:

Of course you could look in /lib/systemd/system to learn it is rc-local  :-) :-)



Thank you; that worked.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/SOSOUQUIB4YP2EDHQD7M6IXFV6IV2EW7/

Re: cpupower

2018-06-24 Thread Ed Greshko 
On 06/25/18 09:21, Joe Zeff wrote:
> On 06/24/2018 05:26 PM, Ed Greshko wrote:
>> Read my reply to poc.  It is a "static" service.  It doesn't need to be 
>> "enabled".
>
> I too have an rc.local script, but it's just a stub, and doesn't even have
> #!/bin/sh in it that's just a stub in case I ever need it.
>
> systemctl status rc.local.service
>
>
> Unit rc.local.service could not be found.

Of course you could look in /lib/systemd/system to learn it is rc-local  :-) :-)

>
> Checking, it's owned by root and is executable.  Maybe I should put something 
> into
> it, such as a printf that's redirected to a file in /root, and see what 
> happens
> next time I need to reboot.
>

-- 
Conjecture is just a conclusion based on incomplete information. It isn't a 
fact.



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/G46SD54WEJ5MRPVJQLMUID6CR4CGQZUZ/

Re: cpupower

2018-06-24 Thread Joe Zeff 

On 06/24/2018 06:16 PM, Roger Heflin wrote:

If you want to debug it the easy way do this:

create /usr/local/bin/slowcpus and make it executable and put the
commands in it and test it from the cmd line:

Then in rc.local do this:


That's a good idea.  I remember reading, once, that you should only use 
rc.local to invoke scripts, not put the command in there directly.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/4OBFAGOC2YYWUKNQBQW567HJLZDXS2V6/

Re: cpupower

2018-06-24 Thread Joe Zeff 

On 06/24/2018 05:26 PM, Ed Greshko wrote:

Read my reply to poc.  It is a "static" service.  It doesn't need to be 
"enabled".


I too have an rc.local script, but it's just a stub, and doesn't even 
have #!/bin/sh in it that's just a stub in case I ever need it.


systemctl status rc.local.service


Unit rc.local.service could not be found.

Checking, it's owned by root and is executable.  Maybe I should put 
something into it, such as a printf that's redirected to a file in 
/root, and see what happens next time I need to reboot.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/VSRBP2HPNXMGKSX3IEAYBDQXKUT25FIA/

Re: cpupower

2018-06-24 Thread Roger Heflin 
If you want to debug it the easy way do this:

create /usr/local/bin/slowcpus and make it executable and put the
commands in it and test it from the cmd line:

Then in rc.local do this:

/usr/local/bin/slowcpus > /tmp/slowcpu.out 2>&1



On Sun, Jun 24, 2018 at 7:26 PM, Ed Greshko  wrote:
> On 06/25/18 08:11, Tim via users wrote:
>> Allegedly, on or about 24 June 2018, Patrick O'Callaghan sent:
>>> Note that you now have to explicitly enable rc.local to make it run
>>> at boot time:
>>>
>>> # systemctl enable rc-local.service
>> I just did that, and nothing more (I hadn't, yet, got around to making
>> a rc.local file and putting anything in it), and got this back in
>> terminal:
>
>
> Read my reply to poc.  It is a "static" service.  It doesn't need to be 
> "enabled".
>
> --
> Conjecture is just a conclusion based on incomplete information. It isn't a 
> fact.
>
>
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/GH425ZDWNWXQSHY57M4EDAGFQPZGHB2I/
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/Y6PSIPAUMX7NDDKLL5HUIPKAXYIWG7LV/

Re: cpupower

2018-06-24 Thread Ed Greshko 
On 06/25/18 08:11, Tim via users wrote:
> Allegedly, on or about 24 June 2018, Patrick O'Callaghan sent:
>> Note that you now have to explicitly enable rc.local to make it run
>> at boot time:
>>
>> # systemctl enable rc-local.service
> I just did that, and nothing more (I hadn't, yet, got around to making
> a rc.local file and putting anything in it), and got this back in
> terminal:


Read my reply to poc.  It is a "static" service.  It doesn't need to be 
"enabled".

-- 
Conjecture is just a conclusion based on incomplete information. It isn't a 
fact.



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/GH425ZDWNWXQSHY57M4EDAGFQPZGHB2I/

Re: cpupower

2018-06-24 Thread Tim via users 
Allegedly, on or about 24 June 2018, stan sent:
> I've thought about buying one of those little fridges and putting the
> system in it.

I remember seeing a page or two about people doing that, many years
ago.  Though I can't recall what their success was like.

I'd be concerned about moisture/condensation.

-- 
[tim@localhost ~]$ uname -rsvp
Linux 4.16.11-100.fc26.x86_64 #1 SMP Tue May 22 20:02:12 UTC 2018 x86_64

Boilerplate:  All mail to my mailbox is automatically deleted.
There is no point trying to privately email me, I only get to see
the messages posted to the mailing list.

ZNQR LBH YBBX!
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/W5IRFZ6LT42ZAP4VD5LWOXFEBE6KSKMH/

Re: cpupower

2018-06-24 Thread Tim via users 
Allegedly, on or about 24 June 2018, Patrick O'Callaghan sent:
> Note that you now have to explicitly enable rc.local to make it run
> at boot time:
> 
> # systemctl enable rc-local.service

I just did that, and nothing more (I hadn't, yet, got around to making
a rc.local file and putting anything in it), and got this back in
terminal:


# systemctl enable rc-local.service
The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
settings in the [Install] section, and DefaultInstance for template units).
This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
   .wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
   a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
   D-Bus, udev, scripted systemctl call, ...).
4) In case of template units, the unit is meant to be enabled with some
   instance name specified.


My intention was to put this in rc.local, so I didn't have to keep
issuing the commands, as root, every bootup:

#!/bin/sh
#

# plugged in SD CARDs have wrong filedates, this is to correct that:
hwclock --systohc --utc
hwclock --hctosys --utc

-- 
[tim@localhost ~]$ uname -rsvp
Linux 4.16.11-100.fc26.x86_64 #1 SMP Tue May 22 20:02:12 UTC 2018 x86_64

Boilerplate:  All mail to my mailbox is automatically deleted.
There is no point trying to privately email me, I only get to see
the messages posted to the mailing list.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/IP5XARE6SWKIMIMLM4DJMWTV4WLPITQH/

Re: cpupower

2018-06-24 Thread Ed Greshko 
On 06/25/18 07:20, Tom Horsley wrote:
> On Mon, 25 Jun 2018 07:07:52 +0800
> Ed Greshko wrote:
>
>> I don't recall how I found my mistake.  I do remember putting in a few 
>> "touch"
>> commands in the script to create files and thereby narrow down where in the 
>> script
>> I'd gone wrong.
> Two things that often cause rc.local failures:
>
> 1. Having a different $PATH as root than as your normal user.
>
> 2. If you are trying to start a long running process
>(Like launch a daemon), the "new and improved"
>systemd will helpfully kill it off for you
>shortly after it is started.
>
> This has led me to transform my rc.local script into this:
>
> /usr/bin/at -M now <<'HERE' > /dev/null 2>&1
> /etc/rc.d/the-real-rc.local
> HERE
>
> Then move everything I used to be able to put in rc.local
> into the-real-rc.local instead (sheesh!)
>
> Oh yea, silliest thing to check:
>
> Is rc.local executable, does the first line start with #!/bin/sh ?

I hope you're not waiting for me to answer that question.  :-) :-) :-)


-- 
Conjecture is just a conclusion based on incomplete information. It isn't a 
fact.



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/6QAECPUPOQN5UH5TGYCNZKBOMGOSQY7R/

Re: cpupower

2018-06-24 Thread Ed Greshko 
On 06/25/18 06:53, JD wrote:
> # systemctl -l start rc-local
> # echo $?
> 0
> #
> # systemctl -l status rc-local.service
> rc-local.service - /etc/rc.d/rc.local Compatibility
>    Loaded: loaded (/usr/lib/systemd/system/rc-local.service; enabled)
>    Active: active (exited) (Result: exit-code) since Sun 2018-06-24 22:49:49 
> Boise;
> 32s ago
>   Process: 17623 ExecStart=/etc/rc.d/rc.local start (code=exited, 
> status=0/SUCCESS)
>  Main PID: 17637 (code=exited, status=1/FAILURE)
>
> Jun 24 22:49:49 localhost.localdomain systemd[1]: Started /etc/rc.d/rc.local
> Compatibility.
> Jun 24 22:49:50 localhost.localdomain systemd[1]: rc-local.service: main 
> process
> exited, code=exited, status=1/FAILURE


BTW, I think you should check the times on this.  If I recall correctly "start" 
will
not work on rc-local since it designed to run just once at boot time.

So, I don't think that "systemctl -l start rc-local" can be used as a 
diagnostic tool.

-- 
Conjecture is just a conclusion based on incomplete information. It isn't a 
fact.



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/P32Z5AMTUM7UVJKBRNEHHKCT4XLJKYHL/

Re: cpupower

2018-06-24 Thread Joe Zeff 

On 06/24/2018 03:55 PM, JD wrote:
Well, rc-local.service cannot be instrumented with echoes from the 
shell, which is run

with option -x in /etc/rc.d/rc.local



Maybe it would be best to do this:  start off with date > /root/log.txt 
(This tells you when you booted and gets rid of any previous file.)  and 
add 2>>/root/log.txt to each commands so that stderr goes into the log. 
Ideally, of course, the file should contain nothing but the date, but if 
anything's wrong, this will give us a hint.



None of those commands are failing.


When you run it by hand.  We're trying to find out what happens when it 
runs (if it runs) at boot.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/QVQPM6YXR2JGU4G3PDTNZMDQGYY46J46/

Re: cpupower

2018-06-24 Thread Tom Horsley 
On Mon, 25 Jun 2018 07:07:52 +0800
Ed Greshko wrote:

> I don't recall how I found my mistake.  I do remember putting in a few "touch"
> commands in the script to create files and thereby narrow down where in the 
> script
> I'd gone wrong.

Two things that often cause rc.local failures:

1. Having a different $PATH as root than as your normal user.

2. If you are trying to start a long running process
   (Like launch a daemon), the "new and improved"
   systemd will helpfully kill it off for you
   shortly after it is started.

This has led me to transform my rc.local script into this:

/usr/bin/at -M now <<'HERE' > /dev/null 2>&1
/etc/rc.d/the-real-rc.local
HERE

Then move everything I used to be able to put in rc.local
into the-real-rc.local instead (sheesh!)

Oh yea, silliest thing to check:

Is rc.local executable, does the first line start with #!/bin/sh ?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/RBLVKZND5RXNWGPQ53YAT57W4EVBXUAL/

Re: cpupower

2018-06-24 Thread Ed Greshko 
On 06/25/18 06:53, JD wrote:
> Well, this is interesting:
>
> # systemctl -l start rc-local
> # echo $?
> 0

Which means the "systemctl" command succeeded.

> #
> # systemctl -l status rc-local.service
> rc-local.service - /etc/rc.d/rc.local Compatibility
>    Loaded: loaded (/usr/lib/systemd/system/rc-local.service; enabled)
>    Active: active (exited) (Result: exit-code) since Sun 2018-06-24 22:49:49 
> Boise;
> 32s ago
>   Process: 17623 ExecStart=/etc/rc.d/rc.local start (code=exited, 
> status=0/SUCCESS)
>  Main PID: 17637 (code=exited, status=1/FAILURE)
>
> Jun 24 22:49:49 localhost.localdomain systemd[1]: Started /etc/rc.d/rc.local
> Compatibility.
> Jun 24 22:49:50 localhost.localdomain systemd[1]: rc-local.service: main 
> process
> exited, code=exited, status=1/FAILURE

Which means the script failed.

>
> So, is there a way to get more detailed info on what caused the failure?? 

I don't recall how I found my mistake.  I do remember putting in a few "touch"
commands in the script to create files and thereby narrow down where in the 
script
I'd gone wrong.


-- 
Conjecture is just a conclusion based on incomplete information. It isn't a 
fact.



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/L4HPJYZC46O5F4SESOW4E224G2OVWU7S/

Re: cpupower

2018-06-24 Thread JD 



On 06/24/2018 04:45 PM, Joe Zeff wrote:

On 06/24/2018 03:12 PM, JD wrote:

​I have enabled rc-local:
sudo systemctl enable rc-local
which is supposed to automagically execute /etc/rc.d/rc.local during 
bootup,
but for some strange reason, rc.local is not being automagcally 
executed,
even though (as I explained already, it is an executable shell script 
with

execute permissions set.

I have to run it by hand.


Strange.  Try putting echo statements in, with output directed to a 
file in /root that will tell you that each command has run or not.
Well, rc-local.service cannot be instrumented with echoes from the 
shell, which is run

with option -x in /etc/rc.d/rc.local

None of those commands are failing.
Please see my reply to Ed Geshko.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/4S5GKEF4TGVBYXJO4DJV4ZMEPLFTRMJC/

Re: cpupower

2018-06-24 Thread Patrick O'Callaghan 
On Mon, 2018-06-25 at 06:38 +0800, Ed Greshko wrote:
> On 06/25/18 05:43, Patrick O'Callaghan wrote:
> > On Sun, 2018-06-24 at 11:25 -0700, Joe Zeff wrote:
> > > On 06/24/2018 10:55 AM, JD wrote:
> > > > On 06/24/2018 11:37 AM, Joe Zeff wrote:
> > > > > On 06/24/2018 10:27 AM, JD wrote:
> > > > > > But I do not want to do this loop every time I boot up.
> > > > > > I want to have set once and for all!!!
> > > > > 
> > > > > There's probably a proper way to do that, but until somebody finds 
> > > > > it, 
> > > > > put that into a shell script and call it from rc.local.
> > > > 
> > > > So far, the ways I have found on google search have not survived
> > > > a reboot :(
> > > 
> > > That's why you use rc.local.  It's a shell script called at the end of 
> > > boot that you can use for any special or non-standard stuff you want or 
> > > need done.
> > 
> > Note that you now have to explicitly enable rc.local to make it run at
> > boot time:
> > 
> > # systemctl enable rc-local.service
> 
> Who told you that?  It is a "static" service and need not be enabled.
> 
> Before creation of an executable /etc/rc.d/rc.local file
> 
> [egreshko@f28k-b1 ~]$ systemctl status rc-local.service
> ● rc-local.service - /etc/rc.d/rc.local Compatibility
>Loaded: loaded (/usr/lib/systemd/system/rc-local.service; static; vendor 
> preset:
> disabled)
>Active: inactive (dead)
>  Docs: man:systemd-rc-local-generator(8)
> 
> After creation and rebooting without enabling.
> 
> ● rc-local.service - /etc/rc.d/rc.local Compatibility
>Loaded: loaded (/usr/lib/systemd/system/rc-local.service; enabled-runtime; 
> vendor
> preset: disabled)
>Active: active (exited) since Mon 2018-06-25 06:32:27 CST; 1min 30s ago
>  Docs: man:systemd-rc-local-generator(8)
>   Process: 652 ExecStart=/etc/rc.d/rc.local start (code=exited, 
> status=0/SUCCESS)
> 
> Jun 25 06:32:27 f28k-b1.greshko.com systemd[1]: Starting /etc/rc.d/rc.local
> Compatibility...
> Jun 25 06:32:27 f28k-b1.greshko.com systemd[1]: Started /etc/rc.d/rc.local 
> Compatibility.#

I'm sure I read that on this list, but it was quite a long time ago so
I may have misunderstood or misremembered. Obviously it was always
static in traditional Unix/Linux systems but with systemd one can never
be sure. Note that the man page recommends it not be used, so I wonder
how long it will continue to be supported.

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/CVWXCSC7CDX72OKONCHYY22SSC4KTFCY/

Re: cpupower

2018-06-24 Thread JD 



On 06/24/2018 04:38 PM, Ed Greshko wrote:

On 06/25/18 05:43, Patrick O'Callaghan wrote:

On Sun, 2018-06-24 at 11:25 -0700, Joe Zeff wrote:

On 06/24/2018 10:55 AM, JD wrote:

On 06/24/2018 11:37 AM, Joe Zeff wrote:

On 06/24/2018 10:27 AM, JD wrote:

But I do not want to do this loop every time I boot up.
I want to have set once and for all!!!

There's probably a proper way to do that, but until somebody finds it,
put that into a shell script and call it from rc.local.

So far, the ways I have found on google search have not survived
a reboot :(

That's why you use rc.local.  It's a shell script called at the end of
boot that you can use for any special or non-standard stuff you want or
need done.

Note that you now have to explicitly enable rc.local to make it run at
boot time:

# systemctl enable rc-local.service

Who told you that?  It is a "static" service and need not be enabled.

Before creation of an executable /etc/rc.d/rc.local file

[egreshko@f28k-b1 ~]$ systemctl status rc-local.service
● rc-local.service - /etc/rc.d/rc.local Compatibility
Loaded: loaded (/usr/lib/systemd/system/rc-local.service; static; vendor 
preset:
disabled)
Active: inactive (dead)
  Docs: man:systemd-rc-local-generator(8)

After creation and rebooting without enabling.

● rc-local.service - /etc/rc.d/rc.local Compatibility
Loaded: loaded (/usr/lib/systemd/system/rc-local.service; enabled-runtime; 
vendor
preset: disabled)
Active: active (exited) since Mon 2018-06-25 06:32:27 CST; 1min 30s ago
  Docs: man:systemd-rc-local-generator(8)
   Process: 652 ExecStart=/etc/rc.d/rc.local start (code=exited, 
status=0/SUCCESS)

Jun 25 06:32:27 f28k-b1.greshko.com systemd[1]: Starting /etc/rc.d/rc.local
Compatibility...
Jun 25 06:32:27 f28k-b1.greshko.com systemd[1]: Started /etc/rc.d/rc.local 
Compatibility.


Well, this is interesting:

# systemctl -l start rc-local
# echo $?
0
#
# systemctl -l status rc-local.service
rc-local.service - /etc/rc.d/rc.local Compatibility
   Loaded: loaded (/usr/lib/systemd/system/rc-local.service; enabled)
   Active: active (exited) (Result: exit-code) since Sun 2018-06-24 
22:49:49 Boise; 32s ago
  Process: 17623 ExecStart=/etc/rc.d/rc.local start (code=exited, 
status=0/SUCCESS)

 Main PID: 17637 (code=exited, status=1/FAILURE)

Jun 24 22:49:49 localhost.localdomain systemd[1]: Started 
/etc/rc.d/rc.local Compatibility.
Jun 24 22:49:50 localhost.localdomain systemd[1]: rc-local.service: main 
process exited, code=exited, status=1/FAILURE


So, is there a way to get more detailed info on what caused the failure??

Thanx!










___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/SZLLVEJJDPC2V3H2IEWXRBTM37FNQSPW/

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/MZZWPBC2MFYJBGMIOJLZWJKAH7OBHPKL/

Re: cpupower

2018-06-24 Thread Ed Greshko 
On 06/25/18 06:12, JD wrote:
>
>
> On Sun, Jun 24, 2018 at 12:25 PM, Joe Zeff  > wrote:
>
> On 06/24/2018 10:55 AM, JD wrote:
>
>
> On 06/24/2018 11:37 AM, Joe Zeff wrote:
>
> On 06/24/2018 10:27 AM, JD wrote:
>
>
> But I do not want to do this loop every time I boot up.
> I want to have set once and for all!!!
>
>
> There's probably a proper way to do that, but until somebody 
> finds it,
> put that into a shell script and call it from rc.local.
>
>
> So far, the ways I have found on google search have not survived
> a reboot :(
>
>
> That's why you use rc.local.  It's a shell script called at the end of 
> boot
> that you can use for any special or non-standard stuff you want or need 
> done.
> ___
>
>
> ​I have enabled rc-local:
> sudo systemctl enable rc-local
> which is supposed to automagically execute /etc/rc.d/rc.local during bootup,
> but for some strange reason, rc.local is not being automagcally executed,
> even though (as I explained already, it is an executable shell script with
> execute permissions set.
>
> I have to run it by hand.
> ​
>

You should then do "systemctl status rc-local" to see if you get (code=exited,
status=0/SUCCESS).  It is possible that the environment isn't the same when run 
by
hand.  Or, there could be another reason why a script would fail in "unattended"
mode.   I ran into that a few years back where it seemed the script wasn't 
running
but in fact was failing for an altogether different reason which I can't recall.



-- 
Conjecture is just a conclusion based on incomplete information. It isn't a 
fact.



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/25K5HPO5DHWNWJVJ4IV5FCEM67IYPBR3/

Re: cpupower

2018-06-24 Thread Joe Zeff 

On 06/24/2018 03:12 PM, JD wrote:

​I have enabled rc-local:
sudo systemctl enable rc-local
which is supposed to automagically execute /etc/rc.d/rc.local during bootup,
but for some strange reason, rc.local is not being automagcally executed,
even though (as I explained already, it is an executable shell script with
execute permissions set.

I have to run it by hand.


Strange.  Try putting echo statements in, with output directed to a file 
in /root that will tell you that each command has run or not.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/W6B5FTAN2IQJFUWX4B2E4M2TR2JSEP4O/

Re: cpupower

2018-06-24 Thread Ed Greshko 
On 06/25/18 05:43, Patrick O'Callaghan wrote:
> On Sun, 2018-06-24 at 11:25 -0700, Joe Zeff wrote:
>> On 06/24/2018 10:55 AM, JD wrote:
>>> On 06/24/2018 11:37 AM, Joe Zeff wrote:
 On 06/24/2018 10:27 AM, JD wrote:
> But I do not want to do this loop every time I boot up.
> I want to have set once and for all!!!
 There's probably a proper way to do that, but until somebody finds it, 
 put that into a shell script and call it from rc.local.
>>> So far, the ways I have found on google search have not survived
>>> a reboot :(
>> That's why you use rc.local.  It's a shell script called at the end of 
>> boot that you can use for any special or non-standard stuff you want or 
>> need done.
> Note that you now have to explicitly enable rc.local to make it run at
> boot time:
>
> # systemctl enable rc-local.service

Who told you that?  It is a "static" service and need not be enabled.

Before creation of an executable /etc/rc.d/rc.local file

[egreshko@f28k-b1 ~]$ systemctl status rc-local.service
● rc-local.service - /etc/rc.d/rc.local Compatibility
   Loaded: loaded (/usr/lib/systemd/system/rc-local.service; static; vendor 
preset:
disabled)
   Active: inactive (dead)
 Docs: man:systemd-rc-local-generator(8)

After creation and rebooting without enabling.

● rc-local.service - /etc/rc.d/rc.local Compatibility
   Loaded: loaded (/usr/lib/systemd/system/rc-local.service; enabled-runtime; 
vendor
preset: disabled)
   Active: active (exited) since Mon 2018-06-25 06:32:27 CST; 1min 30s ago
 Docs: man:systemd-rc-local-generator(8)
  Process: 652 ExecStart=/etc/rc.d/rc.local start (code=exited, 
status=0/SUCCESS)

Jun 25 06:32:27 f28k-b1.greshko.com systemd[1]: Starting /etc/rc.d/rc.local
Compatibility...
Jun 25 06:32:27 f28k-b1.greshko.com systemd[1]: Started /etc/rc.d/rc.local 
Compatibility.



-- 
Conjecture is just a conclusion based on incomplete information. It isn't a 
fact.



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/SZLLVEJJDPC2V3H2IEWXRBTM37FNQSPW/

Re: cpupower

2018-06-24 Thread JD 
On Sun, Jun 24, 2018 at 12:25 PM, Joe Zeff  wrote:

> On 06/24/2018 10:55 AM, JD wrote:
>
>>
>> On 06/24/2018 11:37 AM, Joe Zeff wrote:
>>
>>> On 06/24/2018 10:27 AM, JD wrote:
>>>

 But I do not want to do this loop every time I boot up.
 I want to have set once and for all!!!

>>>
>>> There's probably a proper way to do that, but until somebody finds it,
>>> put that into a shell script and call it from rc.local.
>>>
>>
>> So far, the ways I have found on google search have not survived
>> a reboot :(
>>
>
> That's why you use rc.local.  It's a shell script called at the end of
> boot that you can use for any special or non-standard stuff you want or
> need done.
> ___
>

​I have enabled rc-local:
sudo systemctl enable rc-local
which is supposed to automagically execute /etc/rc.d/rc.local during bootup,
but for some strange reason, rc.local is not being automagcally executed,
even though (as I explained already, it is an executable shell script with
execute permissions set.

I have to run it by hand.
​
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/YPS7LXAJ5X2VF4S773CBT7S5NTXOZW2N/

Re: cpupower

2018-06-24 Thread Patrick O'Callaghan 
On Sun, 2018-06-24 at 11:25 -0700, Joe Zeff wrote:
> On 06/24/2018 10:55 AM, JD wrote:
> > 
> > On 06/24/2018 11:37 AM, Joe Zeff wrote:
> > > On 06/24/2018 10:27 AM, JD wrote:
> > > > 
> > > > But I do not want to do this loop every time I boot up.
> > > > I want to have set once and for all!!!
> > > 
> > > There's probably a proper way to do that, but until somebody finds it, 
> > > put that into a shell script and call it from rc.local.
> > 
> > So far, the ways I have found on google search have not survived
> > a reboot :(
> 
> That's why you use rc.local.  It's a shell script called at the end of 
> boot that you can use for any special or non-standard stuff you want or 
> need done.

Note that you now have to explicitly enable rc.local to make it run at
boot time:

# systemctl enable rc-local.service

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/CKLOOUUTB66JWDXVMDTKSZZFKZC6YLDH/

Re: cpupower

2018-06-24 Thread stan 
On Sun, 24 Jun 2018 11:27:04 -0600
JD  wrote:

> Manpage of cpu power make no mention of the
> selection of governor.
> How can set the governor to be the user mode governor
> instead of the performance governor and not the ondemand governor?

You can check which governor was compiled as default in your kernel by
running grep -i on the config file in /boot for your running kernel.
Because I compile my own kernel, I set that to ondemand as part of the
configuration during the build.  One way to solve your problem would be
to compile your own kernel, and set it to what you want.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/ZN4JHQKEKNICZKKNRDINUSOAXYKLM55W/

Re: cpupower

2018-06-24 Thread stan 
On Sun, 24 Jun 2018 11:27:04 -0600
JD  wrote:

> Manpage of cpu power make no mention of the
> selection of governor.
> How can set the governor to be the user mode governor
> instead of the performance governor and not the ondemand governor?

This might get you closer.  I didn't see anything directly relevant on
a quick scan, but a closer read might reveal something.

https://www.mjmwired.net/kernel/Documentation/admin-guide/pm/cpufreq.rst
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/K4PS46CYVAJ63QUQDDET7PH3PKA5672D/

Re: cpupower

2018-06-24 Thread stan 
On Mon, 25 Jun 2018 03:55:23 +0930
Tim via users  wrote:

> Allegedly, on or about 24 June 2018, JD sent:
> > Reason I am posting this is because the normal speed of the cores
> > is 2.8GHz, and that is causing numerous kerneloops interrupts
> > (overheating).
> > Fans are at full speed all the time, as I can hear them :) :)  
> 
> Sounds like you have inadequate cooling, and that's going to be a long
> term problem that mayn't be avoided by what you're trying to do.
> 
> Hot components need a large enough heatsink to dissipate their heat,
> and it needs to be firmly attached, with heatsink compound filling the
> tiny gap between chip and heatsink.
> 
> Heatsinks need to have a fan, or other heat distribution scheme, to
> make the heat radiate away sufficiently, and quickly enough.
> 
> The case needs to have airflow that brings in fresh air, and expels
> hot air (running a case with the cover off can prevent adequate
> airflow *across* things, likewise with other obstacles in the case).
> Even systems that use liquid cooling still need to move air through
> the computer case, because not everything that generates heat will be
> directly connected to the cooling system.
> 
> 
I've thought about buying one of those little fridges and putting the
system in it.  Some advantages:

- keeps the system cool (set the fridge to 70F (20C), or even lower)
- closes off the noise of the system, I think fridges are quieter
- keeps dust out of the system

Would have to cut holes for the cables, and seal them.  And it would be
bulkier.

One of these days.  Maybe.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/Z2F7LB6ZLUFX7NORMLEOTIT4COC7PRRS/

Re: cpupower

2018-06-24 Thread Tim via users 
Allegedly, on or about 24 June 2018, JD sent:
> Reason I am posting this is because the normal speed of the cores
> is 2.8GHz, and that is causing numerous kerneloops interrupts
> (overheating).
> Fans are at full speed all the time, as I can hear them :) :)

Sounds like you have inadequate cooling, and that's going to be a long
term problem that mayn't be avoided by what you're trying to do.

Hot components need a large enough heatsink to dissipate their heat,
and it needs to be firmly attached, with heatsink compound filling the
tiny gap between chip and heatsink.

Heatsinks need to have a fan, or other heat distribution scheme, to
make the heat radiate away sufficiently, and quickly enough.

The case needs to have airflow that brings in fresh air, and expels hot
air (running a case with the cover off can prevent adequate airflow
*across* things, likewise with other obstacles in the case).  Even
systems that use liquid cooling still need to move air through the
computer case, because not everything that generates heat will be
directly connected to the cooling system.


-- 
[tim@localhost ~]$ uname -rsvp
Linux 4.16.11-100.fc26.x86_64 #1 SMP Tue May 22 20:02:12 UTC 2018 x86_64

Boilerplate:  All mail to my mailbox is automatically deleted.
There is no point trying to privately email me, I only get to see
the messages posted to the mailing list.

Damn, I didn't mean to press *that* button!
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/HPFTR6LSHJUQT7YRTQMSP7O56DDEBKB2/

Re: cpupower

2018-06-24 Thread Joe Zeff 

On 06/24/2018 10:55 AM, JD wrote:


On 06/24/2018 11:37 AM, Joe Zeff wrote:

On 06/24/2018 10:27 AM, JD wrote:


But I do not want to do this loop every time I boot up.
I want to have set once and for all!!!


There's probably a proper way to do that, but until somebody finds it, 
put that into a shell script and call it from rc.local.


So far, the ways I have found on google search have not survived
a reboot :(


That's why you use rc.local.  It's a shell script called at the end of 
boot that you can use for any special or non-standard stuff you want or 
need done.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/VNDUDQ5GWTYFAQQREW6RI24RPI6AGCJC/

Re: Could LightDM be bad?? Ooops!

2018-06-24 Thread Tim via users 
Allegedly, on or about 24 June 2018, Beartooth sent:
> But now it just keeps giving me a login screen, letting me type, and
> (after Enter) going back to the login screen.

I remember things like that, in the past, being associated with the
wrong permissions for the /tmp directory.  The graphics system wanted
to write a lock file, and would get upset when it couldn't.

$ ls -ldZ /tmp
drwxrwxrwt. 16 root root system_u:object_r:tmp_t:s0 400 Jun 25 03:48 /tmp

-- 
[tim@localhost ~]$ uname -rsvp
Linux 4.16.11-100.fc26.x86_64 #1 SMP Tue May 22 20:02:12 UTC 2018 x86_64

Boilerplate:  All mail to my mailbox is automatically deleted.
There is no point trying to privately email me, I only get to see
the messages posted to the mailing list.

Well somebody had to eat the last biscuit.
You're just miffed that it wasn't you.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/H52DWDTSHMOBHXPWLBDZE7UDXZTMJWAD/

Re: cpupower

2018-06-24 Thread JD 



On 06/24/2018 11:37 AM, Joe Zeff wrote:

On 06/24/2018 10:27 AM, JD wrote:


But I do not want to do this loop every time I boot up.
I want to have set once and for all!!!


There's probably a proper way to do that, but until somebody finds it, 
put that into a shell script and call it from rc.local.


So far, the ways I have found on google search have not survived
a reboot :(
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/WHUPDFQJ2DRP5DIJQSQG43FCE7FSONS6/

Re: cpupower

2018-06-24 Thread Joe Zeff 

On 06/24/2018 10:27 AM, JD wrote:


But I do not want to do this loop every time I boot up.
I want to have set once and for all!!!


There's probably a proper way to do that, but until somebody finds it, 
put that into a shell script and call it from rc.local.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/YPSP7WE3IGBKR6UZC35C6HCF4O2PKYLE/

cpupower

2018-06-24 Thread JD 

Manpage of cpu power make no mention of the
selection of governor.
How can set the governor to be the user mode governor
instead of the performance governor and not the ondemand governor?

If I can permanently set that governor, next I want to
set the cpu frequency (for all cores) to 2134000Hz permanently.

Reason I am posting this is because the normal speed of the cores
is 2.8GHz, and that is causing numerous kerneloops interrupts (overheating).
Fans are at full speed all the time, as I can hear them :) :)

When I set the speed manually (as root) like this:
for i in 0 1 2 3 4 5 6 7 8; do
echo2134000  > cpu$i/cpufreq/scaling_max_freq
done

then kerneloops are greatly reduced.
Every kerneloops is accompanied by mce:
So, it has to be the heat.

But I do not want to do this loop every time I boot up.
I want to have set once and for all!!!

Thanx!!!
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/KAJRA7ZXTIHHHKYH7GQOPOZLKMX7PQYJ/

Re: Could LightDM be bad?? (LONG)

2018-06-24 Thread Beartooth 
On Fri, 22 Jun 2018 14:22:13 -0700, Rick Stevens wrote:

[]
> And just a warning: The lightdm display manager has issues with
> pam_kwallet and pam_kwallet5 if they're installed. If you decide to use
> lightdm, edit the /etc/pam.d/lightdm file and comment out any lines that
> reference pam_kwallet*.so.
> 
> Since you're using lxdm you should be fine, but I just wanted to put
> that warning out there. The bugzilla I opened on it hasn't been resolved
> yet to my knowledge.

Done, with thanks! 

I also did the same with my #2, the one I thought yesterday had 
decided to straighten up and fly right. But there the commenting out 
didn't help. That PC is still console only.
-- 
Beartooth Staffwright, Not Quite Clueless Power User
Remember I know little (precious little!) of where up is.


___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/INJ47BE5RSQJ5VF7TNJNTRHV2EEXY6LT/

Re: Could LightDM be bad?? Ooops!

2018-06-24 Thread Beartooth 
On Fri, 22 Jun 2018 20:57:41 +, Beartooth wrote:

> On Mon, 21 May 2018 05:48:24 +0800, Ed Greshko wrote:
> 
>> In actuality you just need one command.
>> 
>> systemctl -f enable sddm   (or whatever new dm you want)
>> 
>> -f = force   which means "When used with enable, overwrite any existing
>> conflicting symlinks."
>> 
>> and no need to use ".service"
> 
>   Bless you, SIR, bless you again, and bless you some more!
> 
>   First I launched dnfdragora on the one machine that still gives
> me a graphical interface (by running F26 Rescue -- 26 no typo, *not*
> 28),
> and used the GUI to install as many display managers as I could find.
> 
>   I noticed that lxdm seemed to be included in many groups. So I
> did dnf install with the console (from Ctrl-Alt-F2) on my #2 machine,
> which had been denying me any GUI, for love nor electrons. Then
> systemctl -f enable lxdm, and rebooted.
> 
>   IT WORKED!!
> 
>   It's not quite working on #3 yet, but I bet it will be in a day
> or three. I've already stopped feeling like I'm riding a bicycle along
> the edge of a cliff. Champagne is definitely indicated.

It did work. I swear it did. But now it just keeps giving me a 
login screen, letting me type, and (after Enter) going back to the login 
screen.

Somebody got another favorite to replace lxdm??
-- 
Beartooth Staffwright, Not Quite Clueless Power User
Remember I know little (precious little!) of where up is.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/M5PG5LD6LYSSXF6RWBTV62B3I6U2UBSO/

Re: SSH private keys?

2018-06-24 Thread Jeffrey Ross 



On 06/23/2018 08:07 PM, Todd Zullinger wrote:

Mike Wright wrote:

On 06/23/2018 01:35 PM, Jeffrey Ross wrote:

my .ssh directory has my private key in a file called "id_rsa" nothing
with .pub on the end and if I understand correctly running ssh will look
for the private key in a few different file names, none of which end
with .pub.


Gotta have both halves.  "ssh-keygen" will give you new keys.

No need to generate a new keypair.  ssh-keygen -y "will read
a private OpenSSH format file and print an OpenSSH public
key to stdout."


Bingo, I had my public key only stored as authorized_keys, I made a copy 
of it as id_rsa.pub and now the keyring is working as I remember.


I now have in my ~/.ssh directory

authorized_keys
id_rsa
id_rsa.pub  (copy of authorized keys)
known_hosts

Thanks, Jeff
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/SJ7SGR2KHFWZ47LUUOPBEH7LX7TS732H/