- Posts: 17524
- Thank you received: 0
THC problem
2 years 4 months ago #302652
by PCW
Replied by PCW on topic THC problem
GRUB_CMDLINE_LINUX_DEFAULT="quiet isolcpus=1 acpi_irq_nobalance idle=poll"
Please Log in to join the conversation.
- acourtjester
- Topic Author
- Offline
- Elite Member
-
Less
More
- Posts: 292
- Thank you received: 0
2 years 4 months ago #302705
by acourtjester
Replied by acourtjester on topic THC problem
Ok after I make the change to the grub as above I then use crontab to create an operation to run the pinirq script a boot time. With a ctrl x to write it.
@reboot chmod +x pinirq,txt
sudo ./pinirq.txt eth0 should there be a @ at the beginning of this line too???
the script is already on the hard drive from the last time I used it
@reboot chmod +x pinirq,txt
sudo ./pinirq.txt eth0 should there be a @ at the beginning of this line too???
the script is already on the hard drive from the last time I used it
Please Log in to join the conversation.
2 years 4 months ago #302707
by PCW
Replied by PCW on topic THC problem
You don't need to chmod +x more than once so
chmod +x pinirq,txt in unnecessary (and will fail
because crontab has no idea where pinirq.txt is located)
Not sure about crontab and sudo
(will it ask you for a password during startup?)
So the systemd method of launching scripts at startup
may be better
Note that sudo ./pinirq.txt eth0 will fail because again crontab
does not know where pinirq.txt is located (you need a full path
or copy pinirq.txt to a standard executable directory like /user/bin/
Also pinirq.txt should probably be renamed just pinirq or pinirq.sh
(it only has the .txt suffix because that's required to be able to post it to the forum)
@reboot is what tells crontab to do the operation only at boot time
chmod +x pinirq,txt in unnecessary (and will fail
because crontab has no idea where pinirq.txt is located)
Not sure about crontab and sudo
(will it ask you for a password during startup?)
So the systemd method of launching scripts at startup
may be better
Note that sudo ./pinirq.txt eth0 will fail because again crontab
does not know where pinirq.txt is located (you need a full path
or copy pinirq.txt to a standard executable directory like /user/bin/
Also pinirq.txt should probably be renamed just pinirq or pinirq.sh
(it only has the .txt suffix because that's required to be able to post it to the forum)
@reboot is what tells crontab to do the operation only at boot time
Please Log in to join the conversation.
- acourtjester
- Topic Author
- Offline
- Elite Member
-
Less
More
- Posts: 292
- Thank you received: 0
2 years 4 months ago #302709
by acourtjester
Replied by acourtjester on topic THC problem
How about @reboot (full path location) pinirq (renamed just ) pinirq
next line ./pinirq eth0
next line ./pinirq eth0
Please Log in to join the conversation.
2 years 4 months ago #302710
by PCW
Replied by PCW on topic THC problem
@reboot sudo pinirq eth0
assuming pinirq is in /usr/bin/
assuming pinirq is in /usr/bin/
Please Log in to join the conversation.
- acourtjester
- Topic Author
- Offline
- Elite Member
-
Less
More
- Posts: 292
- Thank you received: 0
2 years 4 months ago #302712
by acourtjester
Replied by acourtjester on topic THC problem
done deal I can move it and remove the .txt from it
Thanks
Thanks
Please Log in to join the conversation.
Time to create page: 0.046 seconds
