I know, I know, it's only semi-supported, but I use systemd --user to manage my
graphical environment (no DE, just a WM and a few applications). I've written a
system-level service file which calls startx, which in turn calls systemd user
session via .xinitrc:
dbus-launch --exit-with-session /us
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/27/2012 09:44 PM, Øyvind Heggstad wrote:
> I can only see two things that can really help slow down/stop/revert the
> spiral:
>
> 1) Moderation. Get rid of the serial trollers/flamers
> 2) Get more devs and "good" people to join and be active.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/27/2012 04:35 PM, Nicolas Sebrecht wrote:
> Instead of fragmenting more the mailing lists with the hope of putting
> poor contributions out of place for advanced users, let enter the
> technical oriented users into the dev mailing list.
I don't t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/27/2012 12:43 PM, Allan McRae wrote:
> And we are back...
Sir, you've got some yarbles.
IMHO the cause of all these flaming is that arch-general is too, well, general.
What about if we would split this list up into a list for technical questions
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/27/2012 05:40 AM, C Anthony Risinger wrote:
> "you sir, are an arrant sack of shite -- a pitifully miserable sore
> spewing an egregious pus of arrogance and obstinance -- a first-class
> jerk-off!"
Wow, Stephen Fry would be proud.
http://youtu.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I think we all forgot the most fundamental rule in dealing with trolls:
Do *not* feed the trolls!
If you found someone guilty of being a troll, don't argue. Doesn't matter how
wrong he is or how stupid his opinions, he won't change his mind; yo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
I found a strange problem today after connecting my new monitor to my computer.
With the new monitor I am using a multi monitor setup of size 3200 x 1080. But
it seems some applications are having troubles displaying anything beyond the
appa
> The package I wanted is . It is included in Texlive 2012, but
> doesn't work. When \usepackage{specfront}, Texmaker returns an error.
As I see it, there is no package 'specfont' on CTAN. If you meant 'fontspec' for
changing fonts in LaTeX documents, you have to use 'lualatex' rather than
'pdflat
On 02/16/2012 07:13 PM, ianux wrote:
> What's the difference between this syslog-ng.service file and the one
> from syslog-ng ?
> Beside the Alias line, you only duplicate the Sockets line which already
> exists.
Yeah, the duplication was an accident (might have happened out of frustration).
My pr
Oh, and syslog should probably not read from /proc/kmsg
(see
http://lists.freedesktop.org/archives/systemd-devel/2012-January/004310.html)
If somebody still is interested in this, here is my follow-up:
After some digging (it is amazing how little information exist for this, not
even a man page for anything journal related) I came to the conclusion that
journal/socket is not meant for a logging daemon to read from. Instead
journal/sys
To give a few more examples: With syslog-ng reading journal/socket:
- No logging for cron daemon (fcron)
- No logging at all in log/auth.log
- Only some few kernel messages in log/everything.log
- No logging with logger(1)
The list goes on ...
On 02/15/2012 02:30 PM, Giorgio Lando wrote:
> On Wed 15/02/12, 13:28, Christian Hesse wrote:
>>> - Why are the logs read from /run/systemd/journal/socket incomplete and
>>> how do I fix this?
>
>> /dev/log gives the messages only once. If two processes read from there it's
>> just random which g
On 02/09/2012 03:29 PM, Dave Reisner wrote:
> - With the journal enabled (and it is enabled by default), you no longer
> need to run a syslog daemon (i.e. syslog-ng or rsyslog). The journal,
> by default, writes to /run/systemd/journal (meaning logs will poof on
> reboot). If you want to keep
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/23/2012 01:30 PM, Kevin Chadwick wrote:
> The PAM documentation I've found seems incomplete and a bit ambiguous
> especially if you edit /etc/pam.d/other and make it explicit. I've been
> wondering if that has anything to do with the Support comp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/23/2012 12:59 PM, Kevin Chadwick wrote:
> OpenBSDs bcrypt with configurable rounds is awesome by the way and far
> more secure, yet wouldn't pass PCI compliance, how dumb some of these
> certifications are.
I know next to nothing about bcrypt, b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/21/2012 05:06 PM, Don Juan wrote:
> Then if the default is that then why are default system users, such as
> http mail postfix and similar not displaying the $1$ on the shadow file?
> Also according to the wiki it says des is the default and to u
On 11/16/2011 02:51 PM, Bastien Dejean wrote:
> Hey,
>
> I've added the following lines to my .bashrc:
>
> case "$TERM" in
> rxvt*|xterm*)
> set -o functrace
> trap '[ -z "$BASH_SOURCE" ] && printf "%b"
> "\e]0;$BASH_COMMAND\a"' DEBUG >& /dev/null
>
18 matches
Mail list logo
