On Fri, Dec 15, 2017 at 06:59:55AM +0300, Andrei Borzenkov wrote:
> 15.12.2017 01:17, Lennart Poettering пишет:
> >
> > * systemctl gained a new --dry-run switch that shows what would be
> > done
> > instead of doing it, and is currently supported by the shutdown
> > and
> >
15.12.2017 01:17, Lennart Poettering пишет:
>
> * systemctl gained a new --dry-run switch that shows what would be
> done
> instead of doing it, and is currently supported by the shutdown and
> sleep verbs.
>
I though first it was replacement for (or extension of) "s
Hi!
I am happy to announce systemd 236:
https://github.com/systemd/systemd/archive/v236.tar.gz
Enjoy!
CHANGES WITH 236:
* The modprobe.d/ drop-in for the bonding.ko kernel module introduced
in v235 has been extended to also set the dummy.ko module option
numdummies=
On Thu, 2017-12-14 at 20:34 +0100, Lennart Poettering wrote:
> Well, the idea is that /* */ is used for explanatory comments and //
> is left for local, temporary, non-commitable stuff.
>
> i.e. if you are testing some stuff, and want to comment out some bits
> briefly, use //, but if you add expl
On 12/14/2017 01:47 PM, Uoti Urpala wrote:
> On Thu, 2017-12-14 at 13:24 -0500, Steve Dickson wrote:
>>
>> On 12/14/2017 12:48 PM, Uoti Urpala wrote:
>>> On Thu, 2017-12-14 at 12:05 -0500, Steve Dickson wrote:
+Wants=rpcbind.socket rpcbind.target
+After=rpcbind.socket rpcbind.target
>>>
On Do, 14.12.17 21:14, Uoti Urpala (uoti.urp...@pp1.inet.fi) wrote:
> > > +if (j->current_location.type == LOCATION_DISCRETE)
> > > +// only == 0 or not matters
> >
> > Please use C comments, /* */, see CODING_STYLE.
>
> That is a standard C comment... IMO
On Thu, 2017-12-14 at 10:35 +0100, Lennart Poettering wrote:
> On Do, 14.12.17 03:56, Uoti Urpala (uoti.urp...@pp1.inet.fi) wrote:
> > BTW current sd_journal_next() documentation claims "The journal is
> > strictly ordered by reception time, and hence advancing to the next
> > entry guarantees that
On Thu, 2017-12-14 at 13:24 -0500, Steve Dickson wrote:
>
> On 12/14/2017 12:48 PM, Uoti Urpala wrote:
> > On Thu, 2017-12-14 at 12:05 -0500, Steve Dickson wrote:
> > > +Wants=rpcbind.socket rpcbind.target
> > > +After=rpcbind.socket rpcbind.target
> >
> > Is this needed when the service has sock
On 12/14/2017 12:48 PM, Uoti Urpala wrote:
> On Thu, 2017-12-14 at 12:05 -0500, Steve Dickson wrote:
>> According to systemd.special(7) manpage:
>>
>> rpcbind.target
>> The portmapper/rpcbind pulls in this target and orders itself
>> before it, to indicate its availability. systemd automatica
On Do, 14.12.17 12:05, Steve Dickson (ste...@redhat.com) wrote:
> According to systemd.special(7) manpage:
>
> rpcbind.target
> The portmapper/rpcbind pulls in this target and
> orders itself before it, to indicate its availability. systemd
> automatically adds dependencies of type Af
On Thu, 2017-12-14 at 12:05 -0500, Steve Dickson wrote:
> According to systemd.special(7) manpage:
>
> rpcbind.target
> The portmapper/rpcbind pulls in this target and orders itself
> before it, to indicate its availability. systemd automatically adds
> dependencies of type After= for this tar
According to systemd.special(7) manpage:
rpcbind.target
The portmapper/rpcbind pulls in this target and orders itself before it, to
indicate its availability. systemd automatically adds dependencies of type
After= for this target unit to all SysV init script service units with an LSB
header
On Do, 14.12.17 22:17, Michael Chapman (m...@very.puzzling.org) wrote:
> On Sun, 10 Dec 2017, Bjørn Forsman wrote:
> > On 9 December 2017 at 06:56, Andrei Borzenkov wrote:
> > > [...]
> > > Firmware is unaware of MD RAID and each partition is individually and
> > > independently writable by firmw
On Do, 14.12.17 11:55, D.S. Ljungmark (spi...@aanstoot.se) wrote:
> Right, and _that_ causes a far less interesting output from blkid.
>
> /dev/md0: UUID="1492-1FE7" VERSION="FAT32" TYPE="vfat"
> USAGE="filesystem"
uh, why does it output "/dev/md0" as device for this? did you invoke
it for /dev/
Hi all,
I would like to let you know that sdbus-c++, our in-house C++ binding for
sd-bus library, has been published open-source at
https://github.com/Kistler-Group/sdbus-cpp in hope that it will be useful.
Currently, the binding does not cover the entire sd-bus API; it covers the
core, most w
On Sun, 10 Dec 2017, Bjørn Forsman wrote:
On 9 December 2017 at 06:56, Andrei Borzenkov wrote:
[...]
Firmware is unaware of MD RAID and each partition is individually and
independently writable by firmware.
1. "Firmware is unaware of MD RAID". I agree.
2. "... independently writable by firmwa
On Do, 14.12.17 11:44, D.S. Ljungmark (spi...@aanstoot.se) wrote:
> I seem to have the same problem, and here's the output:
>
> [root@spring ~]# blkid -p /dev/sda1
Well, I presume you are mounting /mnt/boot through the MD layer,
right? Hence you need to check /dev/md0p1 or something
instead. /de
Right, and _that_ causes a far less interesting output from blkid.
/dev/md0: UUID="1492-1FE7" VERSION="FAT32" TYPE="vfat" USAGE="filesystem"
On Thu, Dec 14, 2017 at 11:53 AM, Lennart Poettering
wrote:
> On Do, 14.12.17 11:44, D.S. Ljungmark (spi...@aanstoot.se) wrote:
>
>> I seem to have the sam
I seem to have the same problem, and here's the output:
[root@spring ~]# blkid -p /dev/sda1
/dev/sda1:
UUID="01c0c70f-9204-8e4e-f2a7-aa8ec14c4a41"
UUID_SUB="2a820238-597c-bfd4-aa2e-19425f7e8fa4"
LABEL="spring.skuggor.se:0" VERSION="1.0"
TYPE="linux_raid_member" USAGE="raid"
PART_ENTRY_SC
On Do, 14.12.17 03:56, Uoti Urpala (uoti.urp...@pp1.inet.fi) wrote:
> On Wed, 2017-12-13 at 18:40 +0100, Lennart Poettering wrote:
> > On Mi, 13.12.17 00:43, Uoti Urpala (uoti.urp...@pp1.inet.fi) wrote:
> > > correct position, so I don't see why the monotonicity discard would be
> > > needed for t
On Do, 14.12.17 10:03, Joachim Wuttke (j.wut...@fz-juelich.de) wrote:
> On recovery boot, systemd is hanging after printing the line:
> [ ] systemd[1]: Listening on Journal Socket
>
> What is systemd supposed to be doing?
>
> What other software is involved?
> (I may have caused the problem by
On recovery boot, systemd is hanging after printing the line:
[ ] systemd[1]: Listening on Journal Socket
What is systemd supposed to be doing?
What other software is involved?
(I may have caused the problem by inadvertedly uninstalling some packages)
How to debug / to recover?
Some more deta
22 matches
Mail list logo
