Since upgrading to Fedora 21 I’ve noticed that boot time has taken longer. It appears, from looking at systemd-analyse that mandb is the repeat culprit here.
As I can’t really see the point of running mandb on every boot (which would appear to the be case), I’ve remove the service from systemd by running:
And then created a simple cron in cron.daily:
#!/bin/sh
/usr/bin/mandb –quiet
EXITVALUE=$?
if [ $EXITVALUE != 0 ]; then
/usr/bin/logger -t mandb “ALERT exited abnormally with [$EXITVALUE]”
fi
exit 0
Appears to have helped the boot time so far.
There is a seemingly endless topic about Firefox putting ads in (https://lists.fedoraproject.org/pipermail/devel/2014-November/204272.html). The various camps in this disagreement can be summarised into:
Me? Well I guess I’m in the Mozilla need money from somewhere, as they do have people to pay. I’m also a tad annoyed by the positioning of end users are easy to confuse idiots, as they are not.
I’m back doing some rpm packaging for Fedora after a little break. Got 2 on the go, one of which is currently being reviewed. Thing is, the reviewer brought up some good points which I’m addressing, but the documentation is all over the place. Go here for systemd scriptlets info, so there for the latest standard and lets not forget the contradictions.
Is annoy for me, and I’ve be doing rpm packaging for quite a while, so I dread to thing how a new packager copes. And this must waste the reviewers time as well because of the things that are overlooked.
It would be very helpful to have something like a flowchart that outlines the steps needed and links to information on those steps. Personally I find the current wiki packaging details way too verbose, nice simple steps ensures no mistakes. If more detailed is required that can be linked off somewhere else.
Just my 2c worth, but it is something I think needs to be addressed.
The latest package updates managed to break GDM for me. Had this type of problem before on FC-19, and usually breaking out to a VT and running:
systemctl restart gdm
fixed it, or at least got it started. But this time even that didn’t work.
From looking at journalctl -b I could see that gdm’s account had been expired. OK thats odd, so I editing the /etc/shadow file (sorry, I’m old skool) and removed the expire.
Great, gdm account not longer locked, so GDM will start…….erm sorry not.
Bit of googleing and I see that accountsservices might be the issue here, so I ran:
yum downgrade accountsservice accountsservice-libs
And rebooted….hmmm, still not joy, so I tried breaking out to a VT and restarting GDM and….it works.
Very annoying problem that take too long to resolve. Looks like this is a common issue, so I thought I should post the solution that worked for me
Finally got working version of ptpd for Fedora 18/19 and RHEL6. Nice little package even if I say so myself. First for Fedora, hopefully of any.
A tad scary this. Over at The Hacker News they are reporting:
“Russian anti-virus company Doctor Web reported about the first cross-platform backdoor to run under Linux and Mac OS X identified as "BackDoor.Wirenet.1”. This malicious program designed to steals passwords entered by the user in Opera, Firefox, Chrome, and Chromium, and passwords stored by such applications as Thunderbird, SeaMonkey, and Pidgin.
BackDoor.Wirenet.1 is the first-ever Trojan that can simultaneously work on these operating systems. BackDoor.Wirenet.1 is still under investigation.
At launch BackDoor.Wirenet.1 creates a copy in the user’s home directory. To interact with the command server located at 212.7.208.65, the malware uses a special encryption algorithm Advanced Encryption Standard (AES).“