1. I noticed that one can no longer (with v8-2) turn off the computer by clicking the
'turn off computer' button in KDE. I figured out, with help of recent threads, that one
has to run: systemctl isolate poweroff.target. It worked. Is this the correct way?
2. I use privoxy as a proxy and dnsmasq for dns cacheing. Previously, I issued: service
dnsmasq start ; service privoxy start. I presume I must now run: systemctl start
dnsmasq.service ; systemctl start privoxy.service. Is this correct?
On 08/27/2010 10:11 AM, Petrus de Calguarium wrote:
> Where are the logs for systemd? In /var/log/messages, maybe?
I add systemd.log_target=kmsg systemd.log_level=debug as kernel
parameters to flesh out logging in /var/log/messages
after spending two days reading the two fedora mailing lists (fedora
users & fedora devel), i got a list of ideas that need to be
implemented in order to keep the things up:
1. the abililty to turn off the system
2. smart notifications (maybe multilanguage, geolocation-based, &
3. keep a history of the notifications
4. max. number of notifications at the time
5. click able notifications
6. stackable notifications
7. manageable feeds
any issue about any of those points??
Mahmoud Abdul Jawad
I have no regular need to use cvsps any more, so I've released its ownership
in pkgdb for the branches where I was the primary owner. There are co-
maintainers for it, but they did not respond to my mail about whether they'd
like to pick it up earlier this week, so I'm posting here in case someone else
I know its been discussed in the past but there's been reasons not to
drop a default MTA but now that cronie (the last actual dependency)
has support for logging to system logs is there any reason to include
an MTA by default for F-14?