Dear systemd and dracut folks,
with Debian Sid/unstable, using plain device names like `/dev/sda1` in
`/etc/fstab` and `/etc/crypttab` the LUKS passphrase has to be entered
twice. Once it asked by dracut and once by systemd. I did not yet try
with UUIDs and ask first if that is an error?
Thanks
Thanks Tobias for all of the responses. Yes, I am using plain, unaliased
jounalctl on Arch Linux with systemd 216. In fact, I see absolutely no
"Starting" "Stopping" service messages outside of standard triggers. Is
something wrong with my distro? :/ Was the logging changed in 216?
-Alex
On Mon,
On 23 September 2014 01:10, Alexander Groleau wrote:
> Hmm,
>
> This is a fresh installation of arch linux with systemd. What else might be
> terminating my daemons or how might I be able to figure that out?
A cursory search linked that suspicious EOF error message to libvirtd
crashing. If that's
On Wed, Sep 17, 2014 at 04:20:14PM +0900, WaLyong Cho wrote:
> Before start working it, we need some of discussion about how make the
> transient unit. I think we have two options.
> One is, as you said, make systemd-at and the other is add option to
> systemd-run. (e.g. --OnCalendar=, --OnActiveSe
Hmm,
This is a fresh installation of arch linux with systemd. What else might be
terminating my daemons or how might I be able to figure that out?
Thanks,
Alex
On Mon, Sep 22, 2014 at 10:52 AM, Tobias Geerinckx-Rice <
tobias.geerinckx.r...@gmail.com> wrote:
> On 22 September 2014 15:36, Mantas
On Monday 22 September 2014 at 12:43:28, Daurnimator wrote:
> On 22 September 2014 11:33, Daniel P. Berrange wrote:
>
> > The current '--output FORMAT' argument defines a number of
> > common output formats, but there are some useful cases it
> > does cover. In particular when reading applic
On 22 September 2014 11:33, Daniel P. Berrange wrote:
> The current '--output FORMAT' argument defines a number of
> common output formats, but there are some useful cases it
> does cover. In particular when reading application logs it
> is often desirable to display the code file name, line numb
Hi
On Fri, Sep 19, 2014 at 10:56 PM, Emil Renner Berthing wrote:
> On 19 September 2014 22:19, David Herrmann wrote:
>> On Fri, Sep 19, 2014 at 8:26 PM, Emil Renner Berthing
>> wrote:
>>> Don't rely on __WORDSIZE, but just standard LONG_MAX
>>> and INT_MAX from limits.h.
>>
>> Why? The commit
On 22/09/14 17:58, Tom Gundersen wrote:
> Hi Maurizio,
>
> On Mon, Sep 22, 2014 at 11:48 AM, Maurizio Lombardi
> wrote:
>> This patch changes the naming scheme for sas disks. The original names used
>> disk's sas address and lun, the new scheme uses sas address of the
>> nearest expander (if ava
The current '--output FORMAT' argument defines a number of
common output formats, but there are some useful cases it
does cover. In particular when reading application logs it
is often desirable to display the code file name, line number
and function name. Rather than defining yet more fixed output
On 22 September 2014 15:16, Dale R. Worley wrote:
> 2. Systemd includes a tremendous number of features and behaviors, but
> a lot of them aren't documented very well. That's not so unusual in
> Un*x, but if you're introducing something new, nobody has any prior
> knowledge of it, and the lack o
On Mon, Sep 22, 2014 at 2:44 PM, "Jóhann B. Guðmundsson"
wrote:
>
> On 09/22/2014 12:07 PM, Reindl Harald wrote:
>
> Am 22.09.2014 um 13:45 schrieb Jóhann B. Guðmundsson:
>
>> On 09/22/2014 11:40 AM, Reindl Harald wrote:
>
>>> Am 22.09.2014 um 13:28 schrieb Jóhann B. Guðmundsson:
>
On 09/22/2
Hi Maurizio,
On Mon, Sep 22, 2014 at 11:48 AM, Maurizio Lombardi wrote:
> This patch changes the naming scheme for sas disks. The original names used
> disk's sas address and lun, the new scheme uses sas address of the
> nearest expander (if available) and a phy id of the used connection.
> If no
On 22 September 2014 15:36, Mantas Mikulėnas wrote:
>> [Nonsense]
>
> Neither Requires nor BindsTo imply any ordering though. So that might in
> fact *create* race conditions, if both A and B start at once, but A already
> expects B to be available.
[Indeed. That whole paragraph was hastily re-w
Am 22.09.2014 um 16:41 schrieb Simon McVittie:
> On 22/09/14 10:23, Reindl Harald wrote:
>> honestly the messages about "reaching target" are nonsense without
>> a prefix pointing out that it is about a *user session* because it
>> looks like a bootlog every minute
>
> You can tell this is not
On 22/09/14 10:23, Reindl Harald wrote:
> honestly the messages about "reaching target" are nonsense without
> a prefix pointing out that it is about a *user session* because it
> looks like a bootlog every minute
You can tell this is not the system instance of systemd (init) because
its process
> From: "Jóhann B. Guðmundsson"
> > Did you ever ask yourself why your project provokes that amount of
> > resistance and polarity? Did you ever ask yourself whether this
> > really is just resistance against anything new from people who
> > just do not like "new" or whether it contains*valuable*
Am 22.09.2014 um 15:55 schrieb Jóhann B. Guðmundsson:
> On 09/22/2014 12:58 PM, Reindl Harald wrote:
>> i suggest you get rid of that arrogance and some other developers
>> too because it's the reason for the subject and proves that you
>> *do not* care about users as long you have not the same o
On 09/22/2014 12:58 PM, Reindl Harald wrote:
i suggest you get rid of that arrogance and some other developers
too because it's the reason for the subject and proves that you
*do not* care about users as long you have not the same opinion
you are the one demanding a friendly tone from me, well
Hi,
On 22/09/14 15:58, Reindl Harald wrote:
>
> Am 22.09.2014 um 14:44 schrieb Jóhann B. Guðmundsson:
> Then file a bug report against rsyslog and provide a patch which fixes
> the default log filtering in Fedora to your expectation but leave
> systemd out of it.
>>> wow - in any ot
On Sep 22, 2014 4:07 PM, "Tobias Geerinckx-Rice" <
tobias.geerinckx.r...@gmail.com> wrote:
>
> On 22 September 2014 07:57, Alexander Groleau wrote:
> > I have tried the following script as well during my adventures with no
> > success:
> >
> > [Unit]
> > Description=Start/Stop Libvirt Windows Gues
On 22 September 2014 07:57, Alexander Groleau wrote:
> I have tried the following script as well during my adventures with no
> success:
>
> [Unit]
> Description=Start/Stop Libvirt Windows Guest
> Documentation=man:libvirtd(8)
> Documentation=http://libvirt.org
> After=libvirtd.service
Manually o
Am 22.09.2014 um 14:44 schrieb Jóhann B. Guðmundsson:
>>> > Then file a bug report against rsyslog and provide a patch which fixes
>>> > the default log filtering in Fedora to your expectation but leave
>>> > systemd out of it.
>> wow - in any other case the systemd developers saying that
>> the
On 09/22/2014 12:07 PM, Reindl Harald wrote:
Am 22.09.2014 um 13:45 schrieb Jóhann B. Guðmundsson:
>On 09/22/2014 11:40 AM, Reindl Harald wrote:
>>Am 22.09.2014 um 13:28 schrieb Jóhann B. Guðmundsson:
>>>On 09/22/2014 09:23 AM, Reindl Harald wrote:
Am 22.09.2014 um 01:48 schrieb Jóhann B
On 22/09/14 10:27, Jan Synacek wrote:
> If /etc/machine-id is missing on the system, the first open() call
> should probably handle that case. That's actually not true (at least on
> my system), because the underlying filesystem is read-only at that
> time.
*What* is not true on your system?
Are
Am 22.09.2014 um 13:45 schrieb Jóhann B. Guðmundsson:
> On 09/22/2014 11:40 AM, Reindl Harald wrote:
>> Am 22.09.2014 um 13:28 schrieb Jóhann B. Guðmundsson:
>>> On 09/22/2014 09:23 AM, Reindl Harald wrote:
Am 22.09.2014 um 01:48 schrieb Jóhann B. Guðmundsson:
> The reason for increased
On 09/22/2014 11:40 AM, Reindl Harald wrote:
Am 22.09.2014 um 13:28 schrieb Jóhann B. Guðmundsson:
On 09/22/2014 09:23 AM, Reindl Harald wrote:
Am 22.09.2014 um 01:48 schrieb Jóhann B. Guðmundsson:
The reason for increased log entries in the journal is that more things
are happening now since
This patch changes the naming scheme for sas disks. The original names used
disk's sas address and lun, the new scheme uses sas address of the
nearest expander (if available) and a phy id of the used connection.
If no expander is used, the phy id of hba phy is used.
Note that names that refer to RA
Hello,
I believe that the following code is not correct:
src/core/machine-id-setup.c:188-190:
mkdir_parents(etc_machine_id, 0755);
fd = open(etc_machine_id, O_RDWR|O_CREAT|O_CLOEXEC|O_NOCTTY, 0444);
if (fd >= 0)
writable = true;
else {
fd = open(etc_machine_id, O_RDONLY|O_CLOEXEC
Am 22.09.2014 um 01:48 schrieb Jóhann B. Guðmundsson:
> The reason for increased log entries in the journal is that more things
> are happening now since this is what happening when a job is run.
that don't change the fact that a user not acting as
systemd-developer and not debugging his system d
30 matches
Mail list logo
