It was 2014-08-06 śro 14:53, when Sangjung Woo wrote:
systemd doesn't mount smackfs if systemd was compiled without Smack
support. However, the number of mount point entry in mount_setup_early()
(i.e. N_EARLY_MOUNT) is 5 since smackfs is included. N_EARLY_MOUNT
should be 4 because currently
If one of these options gets stated more than once the different
instances seem to be linked by a logical AND, too. This prevents
overwriting these options via snippets in /etc, e. g.
systemd-timesyncd.service still won't run in KVM with a snippet
On 07/08/14 12:23, Peter Mattern wrote:
If one of these options gets stated more than once the different
instances seem to be linked by a logical AND, too.
Yes. This is documented in systemd.unit(5), which also describes how a
drop-in can reset the list of conditions and start from a clean
On Thu, Aug 07, 2014 at 01:23:34PM +0200, Peter Mattern wrote:
If one of these options gets stated more than once the different
instances seem to be linked by a logical AND, too. This prevents
overwriting these options via snippets in /etc, e. g.
systemd-timesyncd.service still won't run in
Hi, I just install Fedora 20 (with systemd 208) and want log,
if possible, without journald, only to rsyslog.
I have this configuration:
'systemd.log_target=syslog-or-kmsg' at kernel command line
'/etc/systemd/system.conf':
[Manager]
LogTarget=syslog-or-kmsg
DefaultStandardOutput=syslog
On 08/07/2014 12:06 PM, Frantisek Hanzlik wrote:
Hi, I just install Fedora 20 (with systemd 208) and want log,
if possible, without journald, only to rsyslog.
It's not possible.
JBG
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
On Thu, Aug 7, 2014 at 2:06 PM, Frantisek Hanzlik fra...@hanzlici.cz wrote:
It's good that I have no /var/log/journal/* files, but
- journald is still runnig (this isn't too imporatant, but when it
is possible work without it, it will be better)
Why do you want this? As Johann very tersely
First, thank you very much for your quick responses.
I had missed the description in man systemd.unit (If any of these
options is assigned the empty string, ... at the end of the paragraph
about Condition*, right?) and a snippet as posted by Michal works (I had
already checked this myself but
Hi,
Should unprivileged processes be allowed to change cgroup?
As I understand it, it is not possible to block processes to
leave a cgroup, but only to block processes to enter a cgroup.
In the following example, session-c4.scope/tasks belongs to root:root
with -rw-r--r-- and
From: Dimitri John Ledkov x...@ubuntu.com
tmpfiles.d files do not depend on /usr present, and in
--enable-split-usr configuration there may be system units
(e.g. shipped in /lib) that rely on tmpfiles.d to be configured
e.g. tmpfiles.d/systemd.conf itself. Hence tmpfiles.d should use
rootprefix.
On 07/08/14 15:21, Dimitri John Ledkov wrote:
tmpfiles.d files do not depend on /usr present, and in
--enable-split-usr configuration there may be system units
(e.g. shipped in /lib) that rely on tmpfiles.d to be configured
e.g. tmpfiles.d/systemd.conf itself. Hence tmpfiles.d should use
Hi,
On Thu, Aug 07, 2014 at 02:06:07PM +0200, Frantisek Hanzlik wrote:
'/etc/systemd/system.conf':
[Manager]
LogTarget=syslog-or-kmsg
DefaultStandardOutput=syslog
Leave 'LogTarget=' to its default value (journal-or-kmsg).
It's good that I have no /var/log/journal/* files, but
- journald
On Thu, Aug 07, 2014 at 02:34:20PM +0200, Jon Stanley wrote:
I'm not 100% sure what happens if there is a backing store,
i.e. does it still store in memory?
No.
Perhaps understanding why you're allergic to the journal would help in
figuring out solutions to the actual underlying problem.
On 08/07/2014 04:12 PM, Leonid Isaev wrote:
Perhaps understanding why you're allergic to the journal would help in
figuring out solutions to the actual underlying problem.
There is nothing wrong with the journald per se, but it's not a replacement for
the classic syslog
Yes it is.
And there
On Aug 7, 2014 9:11 PM, Jóhann B. Guðmundsson johan...@gmail.com wrote:
Arguably one of journals major/only shortcoming compared to what's out
there is it's lack the ability to send syslog messages over the syslog
network protocol but I think it's just a matter of time until it does,
since it's
Hi,
On Thu, Aug 07, 2014 at 06:11:39PM +, Jóhann B. Guðmundsson wrote:
On 08/07/2014 04:12 PM, Leonid Isaev wrote:
Perhaps understanding why you're allergic to the journal would help in
figuring out solutions to the actual underlying problem.
There is nothing wrong with the journald per
On 08/07/2014 07:44 PM, Leonid Isaev wrote:
Hi,
On Thu, Aug 07, 2014 at 06:11:39PM +, Jóhann B. Guðmundsson wrote:
On 08/07/2014 04:12 PM, Leonid Isaev wrote:
Perhaps understanding why you're allergic to the journal would help in
figuring out solutions to the actual underlying problem.
On 08/07/2014 07:32 PM, Mantas Mikulėnas wrote:
On Aug 7, 2014 9:11 PM, Jóhann B. Guðmundsson johan...@gmail.com
mailto:johan...@gmail.com wrote:
Arguably one of journals major/only shortcoming compared to what's
out there is it's lack the ability to send syslog messages over the
syslog
On Thu, Aug 07, 2014 at 08:01:31PM +, Jóhann B. Guðmundsson wrote:
Give me an actual working example how this is solved using rsyslog/syslog-ng
filters
A quick (and probably dirty) way with syslog-ng:
--
% grep dnsmasq /etc/syslog-ng/syslog-ng.conf
destination d_dnsmasq {
On 08/07/2014 08:41 PM, Leonid Isaev wrote:
Sorry for a long reply...
No problem I needed to see how you were thinking/doing this.
So basically you want to log everything to /run ( volatile ) and filter
out everything above a certain log-level and store that persistent in
it's own journal
Hi,
On Thu, Aug 07, 2014 at 09:44:47PM +, Jóhann B. Guðmundsson wrote:
So basically you want to log everything to /run ( volatile ) and filter out
everything above a certain log-level and store that persistent in it's own
journal
( basically store the output from this journalctl -p err
On 08/07/2014 10:42 PM, Leonid Isaev wrote:
Thanks for letting me know aboout this work, but from the above description it
seems rather limited. I brought up the log-levels only as an example. In
practice one needs to be able to filter using_any_ message attribute.
I just used the example to
22 matches
Mail list logo
