You are not logged in.
- Topics: Active | Unanswered
#526 Re: Other Issues » [SOLVED] Where are the refracta scripts? » 2017-05-17 16:52:43
Yes, I found the "refractasnapshot" and "refractainstaller" packages in the experimental repo. Would not have guessed it. Thank you very much, greenjeans.
#527 Other Issues » [SOLVED] Where are the refracta scripts? » 2017-05-17 13:10:13
- GNUser
- Replies: 22
Hello, dear Veteran Unix Admins! I'm running Devuan Jessie on my x86_64 laptop, but can't seem to find the refracta scripts that are now part of Devuan (see https://devuan.org/os/debian-fork/stabl … ce-042017). I installed Devuan several months ago while it was still in beta, but I've kept it fully updated.
Does anybody know where the refracta scripts can be found on my system (or which package needs to be installed to get them)? I've searched my system files and all packages available for installation but nothing contains the string 'refracta'.
#528 Other Issues » [SOLVED] anacron hangs on battery power » 2017-03-24 23:51:48
- GNUser
- Replies: 0
I'm creating this post in the hope that it helps others with this problem, as it took me a long time to solve.
I installed anacron on my Devuan Jessie laptop. I want anacron to run regardless of whether my laptop is plugged in to AC power or running on battery. I dutifully edited /etc/default/anacron with my favorite text editor and changed "ANACRON_RUN_ON_BATTERY_POWER=no" to "ANACRON_RUN_ON_BATTERY_POWER=yes".
If I'm on battery and boot my laptop or resume from suspend, anacron starts as expected and fools you into thinking that all is well:
bruno@devuan:~$ sudo grep anacron /var/log/syslog
Mar 24 13:32:12 bruno anacron[1596]: Will run job `cron.daily' in 5 min.
Mar 24 13:32:12 bruno anacron[1596]: Will run job `cron.weekly' in 10 min.
Mar 24 13:32:12 bruno anacron[1596]: Will run job `cron.monthly' in 15 min.
Mar 24 13:32:12 bruno anacron[1596]: Jobs will be executed sequentiallyTHE PROBLEM
The problem is that if I'm on battery power, anacron never actually runs any jobs--it says that it will (as you can see in syslog), but it just hangs indefinitely and never actually does anything. Here's another look at the syslog, hours later:
bruno@devuan:~$ sudo grep anacron /var/log/syslog
Mar 24 13:32:12 bruno anacron[1596]: Will run job `cron.daily' in 5 min.
Mar 24 13:32:12 bruno anacron[1596]: Will run job `cron.weekly' in 10 min.
Mar 24 13:32:12 bruno anacron[1596]: Will run job `cron.monthly' in 15 min.
Mar 24 13:32:12 bruno anacron[1596]: Jobs will be executed sequentiallyLooking at the timestamps in /var/spool/anacron confirms that no jobs were run.
THE SOLUTION
Such "silent errors" are so tough to solve! I tried everything under the sun and eventually got this idea from somewhere:
$ sudo chmod a-x /usr/lib/pm-utils/power.d/anacronBINGO! Once that wicked script is no longer executable, anacron runs its jobs when it says it will--even on battery power. Here's what syslog shows 16 minutes after a reboot while running on battery:
bruno@devuan:~$ sudo grep anacron /var/log/syslog
Mar 24 18:32:12 bruno anacron[1596]: Will run job `cron.daily' in 5 min.
Mar 24 18:32:12 bruno anacron[1596]: Will run job `cron.weekly' in 10 min.
Mar 24 18:32:12 bruno anacron[1596]: Will run job `cron.monthly' in 15 min.
Mar 24 18:32:12 bruno anacron[1596]: Jobs will be executed sequentially
Mar 24 18:37:12 bruno anacron[1596]: Job `cron.daily' started
Mar 24 18:37:12 bruno anacron[2716]: Updated timestamp for job `cron.daily' to 2017-03-24
Mar 24 18:37:15 bruno anacron[1596]: Job `cron.daily' terminated
Mar 24 18:42:12 bruno anacron[1596]: Job `cron.weekly' started
Mar 24 18:42:12 bruno anacron[2895]: Updated timestamp for job `cron.weekly' to 2017-03-24
Mar 24 18:42:12 bruno anacron[1596]: Job `cron.weekly' terminated
Mar 24 18:47:12 bruno anacron[1596]: Job `cron.monthly' started
Mar 24 18:47:12 bruno anacron[2980]: Updated timestamp for job `cron.monthly' to 2017-03-24
Mar 24 18:47:12 bruno anacron[1596]: Job `cron.monthly' terminated
Mar 24 18:47:12 bruno anacron[1596]: Normal exit (3 jobs run)#529 Re: Other Issues » [SOLVED] apt-file search not working » 2017-03-23 13:23:06
Hats off, fsmithred. Your modification is much more elegant. Very nice.
#530 Re: Other Issues » [SOLVED] apt-file search not working » 2017-03-22 14:30:54
Here's a robust workaround for the time being:
1. On a Debian Jessie system:
$ sudo apt-file update2. Copy /var/cache/apt/apt-file directory from Debian to Devuan
3. Copy /etc/apt/sources.list from Debian to Devuan, renaming it /etc/apt/debian-sources.list in Devuan so it doesn't conflict with Devuan's "real" sources.list
4. Put this in your ~/.bashrc:
alias apt-file='apt-file --sources-list /etc/apt/debian-sources.list'Now apt-file searches work as expected, regardless of whether the package containing the file is already installed on your system or not. We're obviously searching through Debian's packages, but 99% of the time it'll be close enough. Just make sure to run apt-file as regular user, since regular user is the one who has the alias:
$ apt-file search foo#531 Re: Other Issues » [SOLVED] apt-file search not working » 2017-03-18 20:22:37
Very nice, but has one drawback: "dpkg -S" can only search the contents of packages that are already installed on the system. If the purpose of the search is to determine which package to install, "dpkg -S" isn't going to help.
#532 Re: Other Issues » [SOLVED] apt-file search not working » 2017-03-18 15:17:26
Thank you. I'm very happy to be part of this new community--it's truly an island of sanity. I have no interest in making my system orders of magnitude more complex so that I can (maybe) shave a few seconds off my boot time. When it comes to my OS, I'll take something I can more easily understand and control over something new and (supposedly) faster *anyday* 
Long live Devuan!
#533 Re: Other Issues » [SOLVED] apt-file search not working » 2017-03-17 14:12:25
Oops, my bad. Sorry for missing that.
#534 Other Issues » [SOLVED] apt-file search not working » 2017-03-16 16:09:01
- GNUser
- Replies: 16
I use apt-file to find which package contains a given file. This is extremely handy and sometimes is the only way I know to get such information.
While apt-file works flawlessly in Debian Jessie, in Devuan Jessie apt-file cannot find what it needs to build its cache:
bruno@devuan:~$ sudo apt-file update
Ignoring source without Contents File:
http://us.mirror.devuan.org/merged/dists/jessie/main/Contents-amd64.gz
Ignoring source without Contents File:
http://us.mirror.devuan.org/merged/dists/jessie-security/main/Contents-amd64.gz
Ignoring source without Contents File:
http://us.mirror.devuan.org/merged/dists/jessie-updates/main/Contents-amd64.gz
bruno@devuan:~$ apt-file search foo
E: The cache is empty. You need to run 'apt-file update' first.Is this a problem on my end or is something missing from Devuan's repositories? It seems more likely to be the latter. If it's a repository problem as I suspect, does anyone know whether there are plans to add the missing "Contents Files" to Devuan's repositories? Thanks!
Board footer
