Re: [arch-general] Texlive package install
> 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
'pdflatex' for generating pdf-documents.
[arch-general] XServer: Display errors beyond virtual x-coord 2640
-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 apparently magical line of the (virtual) x-coord 2640. The troublemakers so far are: - - GVim which renders no text beyond the magical line. This happens mid-character. vim in a terminal behaves fine. - - Tint2 which shows no application icons in the system tray after 2640. Also happens mid-icon. The clock has no problems. The rendering of icons in xfce4-panel works strangely. - - MPlayer,MPlayer2, VLC, Skype those freeze, but only in the "danger zone"; so they play a partially frozen video - - xterm same problem as with GVim. Other terminals (rxvt, Roxterm) are fine. - - Conky Same as Gvim and xterm Most other applications are not affected by this bug. This problem seems to be independent from the window manager, as it occurs in openbox-multihead, vanilla openbox, i3, dwm and awesome. I am enabling my multihead setup via xrandr: xrandr --output VGA-0 --auto --pos 1280x0 --output LVDS --auto --pos 0x280 Package infos: - - xorg-server 1.12.3.901-1 - - xorg-xrandr 1.3.5-1 - - libxrandr 1.4.0-1 - - libxinerama 1.1.2-1 - - xf86-video-ati 1:6.14.6-1 Further information: xrandr output: https://pzt.me/7o17 Xorg.0.log:https://pzt.me/9fb4 Here are some pictures. As you can see, the text gets cut mid-character, but strangely, the textdecoration is not affected. http://img.vim-cn.com/af/ea943e3e903364fc9fc0d00d7ccd09f980bc40 http://img.vim-cn.com/ed/3ec2f5a955fefccbfa29d9d7b7356ea9669348 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJQKnNDAAoJENVg3RpC7ZC8fDoQALQLvuYhPgAGsxC6pxzLTNQ2 cZoRg+DoC2nFd2dimBYBCWhR/bNITZVwKvh7Wr2YQs3X0C4BcFX6VWUNcB7mj5cO RTNtXIlhwjHMg3B92bRIGbCQdSWlQeTbX+RdKBtJioVHdQR+jcUd8ShbYInbMcOK 2jSM/1P0dAULInAh/tsqPONNaDdPS7bD+tM1u0IyfvwMFUpKVGGgz8DY0i0a/3Oe xKkyG7xWdYLfc1Y2B4TTzQTUykE1MiXd6xlB+ASoJcZMBxqZpGSYrHSe0+lMo0bx emOHBI5iNQPAgG3yDbnC9uvMvKZDSrcifmFj6WoM1cEjXIlOFB63TYJgm2KDzDEl EWmQRr3FSDKmwa5P9jGnCQisIgIkCkodlGK0am683ilTp7Zc108y9joBU39IkynA U9eKBg8aCSS0bCpBeBbvGmJKPjH+VtTCpnZ0EXTXeuNzh9TkSpt17q+XyCDXDht/ 3kaXGvhsY6twR7EzGSvcf6hc524GoFd6xb0cY1uJxvFb2f+7IU5C2hmndVi3SbBR H8gwNrxCO7oayhLLe/44DjkMKPrHOSPEQOVEEN48nVYmmIUQjzn2+K8r5KVULFsM ISwFHfWMR0j8EcBN/u/gWEdMCHv3bW4q0hs7bdyUGBjY7hdchmJ53DGvkMI//HIU h9uF1N+qQCEobiwkWFvR =GfOd -END PGP SIGNATURE-
Re: [arch-general] Arch-general is becoming a mess !
-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; you're just wasting your time and energy. If someone just posts something just for the sake of flaming and spreading FUD but no one is reacting, he's going to leave. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJQLSQeAAoJENVg3RpC7ZC8RjcQAIvhL/C8Jbnrfp53N8tpow0f ItLuozBwoICDkTnoix+AmD3M6EHciwmvj4EhCbe/Tk90VDTDXzkbiAkvA09dqjvm 0PAfnZmdo0T64PKqncFL2pxd7c7/5eLL4p0o4LkShM5zVXqXJKVC1BZ57Qc7zmSR aDzzaOBEktUnLbQfbvuwSeW8u7yM33AxiIVSw+roU8PnnUEFkWrKmTOR58F7NI33 uB/BLCEmVqaW/HfuL6z5Zbkuql6eUFYMiVII4ZyjcKg5AkIRHVXb2LXgTjl1A4eK SjGPLbSsSoZxc89WlE/3sUuanpLl22jdwWDoAA7A1zrQirKB8LqvAURJqvSQcHLF EK8/EhtEg4eDjkuGSlwsYo16NOeLVzd8Ktwat703zlvcDn1mlRYj2mfhAo8e3AlY cTPridE/fVoS1q8QvYURwDQkl4mtuQ7QlvdZMvSRrXZIQnKY+L4PKcZVXVIB10jy glhr1jJtgcUKVbI7KbC319yBGAdU2QoGztbbj7/hqe/aXLyBNoX5VnT9s7BZOsrz 4Z3NQdT4ncyE7kpb2LMpz2wCxiPVumQBQd3HVOk1LY+vEHzVZOS0fcyunXfc+LQY 3fss1JBkCqn6Dqiqhk6+lkO3qZrT5iQ6D/c++JmWwXDYu4N0MprTrQ88OnXmM+kl Xx5W036v0doeMDERULmD =KNIb -END PGP SIGNATURE-
Re: [arch-general] SystemD poll
-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.be/H0cJBEMiN1c -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJQPI/HAAoJENVg3RpC7ZC8goQP/jp8i3PvWxLfzNLh9+wzdmY2 Z1LI0Kc8W+aV8khWCzzRUsCbUgYlPCco+R1ui+co534R85PrvajxGKC99DU7pj6s o4b5w9dhds6fD0LTkNRH2m6TgqJ3YeJrC+5VWjxV9ey/j2AFFIsGQBCgyM6w0S5C QiHukol8RY0Mywx94tITIkJSHYffuIqUlB35a7yzhkCgGyVmPOSvbvVlDhxY4ilG vEAg9BPU9Y2TG5gZO1GPi+zugEdE0ePnNV0iSuJOnKfvjHCYfyPXjVlBZoidr4+Z 1cKjrNqONg+OBbgOOT4krW9LGf7jxFKLANThIw771bpsKmRNWhgjVT3dxfkD1uHS p2KIrGqiTVAcgCGC5zGhknBzno6GTQtO1QXgHvsjpg+1ybc/vRaDKdb+CkSrHKEC GkEww0RgoLLLP0upsIsFxIB18cumxghUnl5GlsW8Gf07yKNK39f+zebtxUZmJ3+4 FNQ94KhsAEykeGb/p4wb9hAxPdzQJaTb2pU3DdSBOChprRLN2YxVycCz0NjufO+a irWIm/GKjxvxqauW/enDaJxoNWCt6xOyxE6tgm1dVoWpjN5bWJnGvxcyDqRw8xmY oEe4Ola0do0zTixavjkoOHRmA+xVypZ6+F32Ja/xU4PluLoty3MHjF5JZZrJdlGJ 63scVfw3n3ARxpdY8Kl3 =QxDD -END PGP SIGNATURE-
Re: [arch-general] Mailing list closed for 24 hours
-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 (e.g. arch-support) and a more philosophical, rambling one (e.g. arch-discussion), so that everyone could choose his/her own poison? P.S.: This is definitely a help request to make the make the arch mailing lists a happy place again ;-) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQIcBAEBAgAGBQJQZERPAAoJENVg3RpC7ZC86KAQAKT7ST6PgVX+ColdBmpttD4/ auwihWnNJ7S8I7BRHGUHV0cXi8puM9z9s1zGCV22NSv+i6ibnvGMWMRfs8/YqR5D +botAqt7/6/HEIDqbGq2f63sY5G8Y5mnmLYDRiwZDwo8XMoPNbVkaHxJC6PNkc7Y FPsHYDe83bMIBRl3u0CMV1zs/sMVyBJPOFAuvAlUebW0FtQVbdLuPu15i2tTIGIv SVnc+bdY5n68hm22ybQG+yPwcQnuq8JOUyFrckEIFkHBmhFLkgUxs3hm+SNUndnL kWubGUUMU/L48zAZJGdfoQ9owod9PIBaF9kVbz+ORcrhsulqnFGzkwOlpg7F039X FxBPtgMfMe2tif7UEcsqxX1w1hiXDxSPNyE2EUMjA+6mmVtyHog00DicDWpPbL9l 2/+O9DHoaoI4sL204H6EayFf1ZpR1Y6aQpxjH7OWDNgaRem/+Sux0HkbLjv90EWt Qre4I5YZcb7837Fw74uV/fsaL9Ee5NHOBR9Lu5NG8lm7J38QmWJyRlcanaGTFZCZ lrXVvk++Ss1e+o+LsXEpxcX40j+EjsMbNLfLifsQD+NaknuDXWpDvUzsrDqiij6s Eb+xbCq/qAy55xxhwT2UFdl8L9ALhHUVB24hGXdAtjzi1poH0fmAtntI/RVtGb/D gsgmX61jX6yFJIL8HkM8 =jKI5 -END PGP SIGNATURE-
Re: [arch-general] Mailing list closed for 24 hours
-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 think that opening arch-dev-public for everybody would solve our problems, it would just relocate the noise into this list. The devs and TUs really need a quiet list of their own with a good signal/noise ratio. (There is no arch-dev-secret, is there?) So what if there was a arch-technical list instead of a arch-support, where all the help request could land and also *purely* technical contributions from advanced users? dev-public could stay as-is with reports and other official stuff, technical would be the list for support and contribution and discussion for rambling and flaming :-) The thing is, some users really want this kind of heated debate, and the only alternative we currently have is banning, which some consider censorship, or shutting the list down for a day (still, awesome!). With the new split there would be the alternative "guys, stay on topic or take is to -discussion". -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQIcBAEBAgAGBQJQZGohAAoJENVg3RpC7ZC8qSsQAMyu4+T8xWmXczmB+PehnaRZ g1aVUIEKxyXXi7MAg/nNU+tWqCo+RpVavFyoRJWpv9+NWUlRjNKB/ReTIjvTebBU rClb8TnWTaKMejG9mMtGZd1zoqJBomTmNYdTEpVurNxEfp79wXOnNPIp0QrPvFZW K/ZTEbtSt/iChy3LRqTuJkAp4nc4yv4MvwQ0fyE2h952Dwg0B2ZOKc5TdYmsjIE3 U2Hb+0XxFwLZlLcKCaob4s0y9dCEMRQ6Yb07hEOlcuxfoi3D0zeaPtv1+yerasqv 2HeaD17iXSGJFhO88bp6ycv+MrNXgM3KD81O7hnjNjfBYXg6UtoCb05JHPcKPaR1 1TW/z5/8MzU45T2C0UQWpNhimDGrb6uLyFAITLYFjLlnkGnsHxOxdgRivRfLEjS6 dOKOvY0K8okI5R0PRcCQjS87LmFm9fs/U4SfJiQZS9Z4m4gs/F7wbTsV2lJ+aecx xRKjOO1ER8Bldz0NKgiSuOI/7H4c4AVw8hkhP2Oi/NcwH5zLiQxZCdbGG9FM9Xr+ yIVhxJYTPP3UtaZrvCWhAsg6yvDa3agHy9yJWJWCw7HnLt6VI+SO3XeH0hGb/1p5 BlB+6HOn1ABtHLZXb1RCi/Pkphd9hikAI/ozbBYiNhb+u2IkQoplDUsFty20CTiU /ggbHX9i3Jxn62nV9/VW =sfRb -END PGP SIGNATURE-
Re: [arch-general] Mailing list closed for 24 hours
-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. For your last point: Thats putting the horse behind the cart. Most devs and/or skilled users leave -general just because it has become such a dump. Concerning moderation: See my last mail. Some users will always going head first into heated discussions. The -discussion mailing list could serve as an outlet for this need, rendering the other list more productive via being moderated; The rule wouldn't be "shut up or be banned", which shouldn't really be necessary for rational folks like us, but "shut up or take this to -discussion" with banning as ultima ratio. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQIcBAEBAgAGBQJQZJw4AAoJENVg3RpC7ZC8o6YQANGIaXG7lURFDQp5ji82bopt nhN6brOcQkBNKeGw2l37f8jTwWwggU5H/PFogOSRGxuN3pYn4Q3xznNFwqA5OmrS GnnqfEX/AUIhN41EOqC3VgrPNomrJg79PB4C37e+k6TbW8T6yBTYBJdtdkksiT+S F/d3rwHeHSYt07EAWFmCoKg18yxW8yGt7dvsnWvm+DLCe9VkfSxHP1zDgMr31ZX5 +33PAG7JZIUp6olJ0Oqp83mJexaJiU0rO7jp8gBKWe02XklAGTxElGqRXtSdaR8O jBEJMIhx2fw84cZP36GYpK1QV3hAInNuWHju9ce4zxI4HJ7vkbGkspz80Kwv76H/ hRo/DjUChyb3seM3f7VNupBKznKx8EhsoUWa+Wem0xMNAJVsYVDWcpEeyGtP5Rl5 5abUxk1/vg2K228TKXc80wc2a0U3HbaoV22sLCDCGzEj//vWpvSY7Q3CEyi8S1+H OCY5KhBZR1f8tkWF0B2bf2J8twy1VRYWLRMLey4/RJitHRXyWKIjD5JciWeNk3SW IU9hPfNjlKm9cE+56e3MvB58Zav5QtdtcL123SqBe1hArHy9Nn7m6VrUcHeF4Orv BFQJMUJU1XUQR/g0z/zODYqSF6Yvmu/gfWSNM6nTOmb4Mrj6qqo1iIjGwEwMOSaT OQOeBbPtGDwlfL/Hmf0L =nJzp -END PGP SIGNATURE-
[arch-general] Quo vadis, systemd user session?
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 /usr/lib/systemd/systemd --user The recent systemd update removed support for direct manipulation of cgroups. I had to rewrite the service file, cannibalized user@.service and ended up with this [1]. Yeah, it's cargo culting, but my mortal brain sometimes can't grok systemds complexity. So my first questions are: Is this something a sane person would do? Is there a more elegant way without installing more 3rd party software? Do I need to involve logind in some way? Part 2: Systemd now calls user@.service with every login, which in turn calls systemd --user. But as I said, I use it for graphical stuff, so I do not want this behavior. So the second bunch of questions would be: Can I overwrite user@.service without breaking something else? How would I do that? Any kind of held is appreciated. The current state of my setup feels kinda frail. Regards, Tobias [1] http://pastebin.com/raw.php?i=jTjTwQMz
Re: [arch-general] Dynamic Titles in urxvt (bash) Without Side Effects?
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
> ;;
> esac
>
> (It sets the current title of the current window according to the last
> ran command.)
>
> But alas, it generates side effects, if I issue this:
>
> ls "$(ls -1 | head -1)"
>
> I get:
>
> ls: cannot access foo.bar: No such file or directory
>
> Strange or trivial?
>
> Cheers,
I don't know much about parameter modifiers in bash, but in zsh this
works for me:
title () {
1=${(%)1}
1=${(V)1}
1=${(q)1}
case $TERM in
screen*)
print -n "\ek$1\e\\" ;;
linux)
;;
*)
print -n "\e]2;$1\a" ;;
esac
}
The (%) modifier expands % escapes like in a prompt expansion (so %~
becomes the directory), (V) makes any special characters in the
resulting words visible (so a newline becomes \n) and the (q) modifier
quotes special characters with backslashes.
Don't know if this may help you.
Re: [arch-general] Upgrading password hashes
-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 upgrade the > hashes out of the default. Am I not understanding it correctly in the > wiki, and the users that I am talking about the hashes do not matter? > Sorry feel confused at the moment. > A ! or x as the hash in /etc/shadow indicates that login for these user is not permitted. (Also you may login using ssh-keys). The CRYPT setting from /etc/default/passwd is only used if pam is not enabled. If it is enabled, the used configs are in /etc/pam.d (e.g. passwd, login etc.) which default nowadays to sha512. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPGuy+AAoJEEDINPnaM7l+QGYH+we8QwHXO8OsAOEibRRAHz2j hwWnXpitJVDLuxJ406F4DtbxXLMD2addtC1tQtSvKhcLAj1Q3bGoCEETqpUaSBTh ZhZOeqBKKyP0BR980Qy3DRSHFWDkWY8ZpwgmutNj7QmmJt3NOwfdSZhzXVbqlx/u vu3BsKAwuAeIE60HbJS4Ugn8VdUlY3HSp1EW0eR2sxb2x81y/T7YW7koBk6aVCv5 6pFqO8S+tgBQnh+5bvagBWvJq1zGGTA1A9sjCEYadynqEVjIY0i5ydsLQ2J+dhUG hiWaGQu4JKBK7meAv5OBtfoewFEVQb4qYqYn1R1D4/Y1IuwTS60SW6nSO/UJrsw= =Dcl9 -END PGP SIGNATURE-
Re: [arch-general] Upgrading password hashes
-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, but you can configure rounds in pam too: password required pam_unix.so sha512 shadow nullok rounds=99 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPHU39AAoJEEDINPnaM7l+/UYH/11e5JPq2CE5yWTsNfcDFa67 R6YOJppkE+de4kYedkx0WOg6zTZ1GwQohbrFYJU7XPhNqQCGM0z5Q5bRbBJQbQee bdUJcVjtpwEFFk6+F86/ArW0N3+MLRB+v5eebzzE86JFCtES1op44sJadtsDlqgE QZFCPnKn7Pz3FxLgxW2k0jJAxA7VyLX3MgMUCgTmpqcYfq7OibFTQ+4nMQhVwmVK eUbb5Tw6DCwKG0qJrBInsEfP/nScrYd2Wew2kYmei1tVpy1LfddfJYWYuKc1sXz3 WQHKfbQ31Dp8ZhgehXdH7x3+Yuw+nmUsNpnrlBMD0RekZGvZt6wYKpkqF1xsE3M= =bXbX -END PGP SIGNATURE-
Re: [arch-general] Upgrading password hashes
-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 companies that are > so involved with Linux, with it paying to be less straight forward. Do > you know of a good reference for PAM? The rounds options is documented in pam_unix(8). If you want something along "The Sysadmins Guide to PAM" search for pam at http://www.linuxtopia.org, they have some manual from SLES, Red Hat etc. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPHVZ4AAoJEEDINPnaM7l+mZIIAI1fbGJiGhnxvr1+N+I9BNPT RuGifa5BqLKDhFP9L+vSghTxRdpVXV9M/HCFpMISX77pm4g0eP7+dtfV2ZF12pa0 gOEIZcg7AFQa0KFCt2JQAJzpjgAM6ntg42RqIQNFdUWKYfHsjCMpUEdoJpDfd/Gk baGW3u8hCzYY3rbo2BYTPAnnISqLpZ6RHqiFAihB6n1lzA8587kkZRql6TxK2gr4 O+3ggwkUX57lL353kvPK2cZUfUf3cIJpsGjxHIQlltZrvhWcZN8bSzk8hwOlW9YZ jYKaqf3I49kc08ivC93OxzCVoASRm6IsURENMi9XN/9gbt2LLZPYS4hUzoXxhg0= =uJAF -END PGP SIGNATURE-
[arch-general] systemd's journal and syslog-ng
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 your logs, simply create
> /var/log/journal. If you really want to keep using a syslog daemon,
> you must tell it to read from /run/systemd/journal/socket, NOT
> /dev/log.
I know I do not longer need to run a syslog daemon, but I like my logs in human
readable form. So, being a obedient ml reader, I configured my syslog-ng to read
from said new socket
unix-dgram("/run/systemd/journal/socket");
instead of the old /dev/log. But since then my logs are incomplete at best. So
here are my questions:
- Why are the logs read from /run/systemd/journal/socket incomplete and how do
I fix this?
- Why do I even have to change the socket? /dev/log is still there and still
works like a charm.
Re: [arch-general] systemd's journal and syslog-ng
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 gets which messages. Probably that is why your logs are >> incomplete. Changing syslog to read from systemd journal's socket should fix >> this. > > It seems to me that he is saying that they are incomplete JUST when reading > from systemd journal > Giorgio exactly
Re: [arch-general] systemd's journal and syslog-ng
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 ...
Re: [arch-general] systemd's journal and syslog-ng
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/syslog should be used (see [1]). So your service file should look something like this: [Unit] Description=System Logger Daemon [Service] Sockets=syslog.socket ExecStartPre=-/bin/systemctl stop systemd-kmsg-syslogd.service ExecStart=/usr/sbin/syslog-ng -F ExecReload=/bin/kill -HUP $MAINPID Sockets=syslog.socket StandardOutput=null [Install] WantedBy=multi-user.target Alias=syslog.service And syslog should read from /run/systemd/journal/syslog [1] http://lwn.net/Articles/474968/
Re: [arch-general] systemd's journal and syslog-ng
Oh, and syslog should probably not read from /proc/kmsg (see http://lists.freedesktop.org/archives/systemd-devel/2012-January/004310.html)
Re: [arch-general] systemd's journal and syslog-ng
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 prior setup lacked the journal/syslog socket, so I thought that the service file was missing a Sockets= entry (reading the file might have helped ;-) ). The service file shipped with syslog-ng does the trick, as long as you point the config to journal/syslog. As for the Alias line, consider this comment from syslog.socket: # The default syslog implementation should make syslog.service a # symlink to itself, so that this socket activates the right actual # syslog service. # # Examples: # # /etc/systemd/system/syslog.service -> /lib/systemd/system/rsyslog.service # /etc/systemd/system/syslog.service -> /lib/systemd/system/syslog-ng.service # # Best way to achieve that is by adding this to your unit file # (i.e. to rsyslog.service or syslog-ng.service): # # [Install] # Alias=syslog.service
