On Wed, Jan 25, 2012 at 11:40 PM, Lennart Poettering
wrote:
> On Wed, 25.01.12 23:12, Tom Gundersen ([email protected]) wrote:
>> In addition to the initrd interfaces for fsck and shutdown (but they
>> are not in the table).
>
> Well, they are included in the "initrd interface" item, the "flag files"
>
On Wed, 25.01.12 23:12, Tom Gundersen ([email protected]) wrote:
> >> The Arch Linux native initscripts just recently adopted your
> >> /etc/locale.conf file, and could go in the "Known Other
> >> Implementations" column for that.
> >>
> >> https://wiki.archlinux.org/index.php/Locale.conf
> >
> > Thank
On Wed, Jan 25, 2012 at 10:46 PM, Lennart Poettering
wrote:
> On Wed, 25.01.12 13:04, William Swanson ([email protected]) wrote:
>
>>
>> On Wed, Jan 25, 2012 at 12:01 PM, Lennart Poettering
>> wrote:
>> > Many of these APIs are already in heavy usage by applications and 3rd
>> > party code.
>>
On Wed, 25.01.12 13:04, William Swanson ([email protected]) wrote:
>
> On Wed, Jan 25, 2012 at 12:01 PM, Lennart Poettering
> wrote:
> > Many of these APIs are already in heavy usage by applications and 3rd
> > party code.
>
> The Arch Linux native initscripts just recently adopted your
> /e
On Wed, Jan 25, 2012 at 12:01 PM, Lennart Poettering
wrote:
> Many of these APIs are already in heavy usage by applications and 3rd
> party code.
The Arch Linux native initscripts just recently adopted your
/etc/locale.conf file, and could go in the "Known Other
Implementations" column for that.
Heya,
to be nice to those who are interested in maintaining a level of
compatibility with the interfaces we have introduced with systemd
without making use of systemd, I have put together this extensive (and
hopefully comprehensive) table:
http://www.freedesktop.org/wiki/Software/systemd/Interfac
Hi all,
I'm trying to get a .target working as a "trigger one action then go
back to not activated state" and despite Lennart help on IRC, it keeps
failing, so it might indicate a bug :
foobar.target :
[Unit]
Description=my trigger target
BindTo=myaction.service
myaction.service:
[Unit]
Descript
On 01/25/2012 05:34 PM, Bill Nottingham wrote:
Michal Schmidt ([email protected]) said:
We could make "systemctl start ..." dump a few of the service's
lines from the journal before exiting.
At that point you're then trying to define heuristics about what the proper
value for 'a few' is, and
On Wed, 25.01.12 14:49, David Thurgood ([email protected]) wrote:
>Dear Sir,
>I am hoping that this is an appropriate place for a "feature request" with
>respect to the program hwclock.
>
>This relates to a very old problem, which as I remember goes back to the
>PC's of the
Michal Schmidt ([email protected]) said:
> On 01/25/2012 03:57 PM, Lennart Poettering wrote:
> >On Wed, 25.01.12 11:11, Jan Engelhardt ([email protected]) wrote:
> >>I would actually prefer if it wrote that to the current tty that
> >>invoked the start action, rather than the console which is s
Hi David,
On Wed, Jan 25, 2012 at 3:49 PM, David Thurgood wrote:
> I am hoping that this is an appropriate place for a "feature request" with
> respect to the program hwclock.
hwclock is part of the util-linux package, so you'd probably have more
luck emailing . systemd does not write to
your rt
On Wed, 25 Jan 2012 16:43:35 +0100
Kay Sievers wrote:
> On Wed, Jan 25, 2012 at 16:33, Mike Kazantsev wrote:
...
> >
> > Not sure if it has to be abstracted via localstatedir or something, but
> > since it's hard-coded in logind anyway, I thought not to bother with it.
> > logind-install-data-h
On Wed, Jan 25, 2012 at 16:33, Mike Kazantsev wrote:
> Good day,
>
> Another issue I've spotted with logind on my system.
>
> "systemd-loginctl enable-linger" goes to src/login/logind-dbus.c:1191,
> which seem to do:
>
> r = safe_mkdir("/var/lib/systemd/linger", 0755, 0, 0);
>
> ...and fails, pro
On 01/25/2012 03:57 PM, Lennart Poettering wrote:
On Wed, 25.01.12 11:11, Jan Engelhardt ([email protected]) wrote:
I would actually prefer if it wrote that to the current tty that
invoked the start action, rather than the console which is stowed
away in a deep cellar...
We explicitly want to
Good day,
Another issue I've spotted with logind on my system.
"systemd-loginctl enable-linger" goes to src/login/logind-dbus.c:1191,
which seem to do:
r = safe_mkdir("/var/lib/systemd/linger", 0755, 0, 0);
...and fails, producing something like "D-Bus call failed: No such file
or directory"
Dear Sir,
I am hoping that this is an appropriate place for a "feature
request" with respect to the program hwclock.
This relates to a very old problem, which as I remember goes back
to the PC's of the 70's and 80's. My present PC seems to have
just
Good day,
Problem is that "systemd-loginctl activate " gives
something like "D-Bus call failed: Operation not permitted", while
strace of logind process looks like this:
epoll_wait(4, {{EPOLLIN, {u32=3, u64=3}}}, 1, -1) = 1
epoll_wait(9, {{EPOLLIN, {u32=166352544, u64=166352544}}}, 1, 0) = 1
rec
On Wed, 25.01.12 11:11, Jan Engelhardt ([email protected]) wrote:
> >[v39]
> >* If a group "adm" exists, journal files are automatically
> > owned by them
>
> This sounds like it has the potential that journal files suddenly
> beomce writable by a random user group that has existed previously.
On Wed, Jan 25, 2012 at 12:39 PM, Tom Gundersen wrote:
> I noticed a regression in the automount handling that I could not
> immediately figure out. I know for a fact that this used to work "a
> long time ago", and that it does not work with v39, but I have not
> bisected further.
It seems this w
On Wed, Jan 25, 2012 at 12:59, Michael Biebl wrote:
> Am 25. Januar 2012 12:00 schrieb Kay Sievers :
>> On Wed, Jan 25, 2012 at 11:11, Jan Engelhardt wrote:
>>> On Wednesday 2012-01-25 02:02, Lennart Poettering wrote:
>>
[v39]
* If a group "adm" exists, journal files are automatically
>>>
Am 25. Januar 2012 12:00 schrieb Kay Sievers :
> On Wed, Jan 25, 2012 at 11:11, Jan Engelhardt wrote:
>> On Wednesday 2012-01-25 02:02, Lennart Poettering wrote:
>
>>>[v39]
>>>* If a group "adm" exists, journal files are automatically
>>> owned by them
>>
>> This sounds like it has the potential
Hi guys,
I noticed a regression in the automount handling that I could not
immediately figure out. I know for a fact that this used to work "a
long time ago", and that it does not work with v39, but I have not
bisected further.
Entries from fstab:
/boot ext2noauto,comment=systemd.autom
On Wed, Jan 25, 2012 at 11:11, Jan Engelhardt wrote:
> On Wednesday 2012-01-25 02:02, Lennart Poettering wrote:
>>[v39]
>>* If a group "adm" exists, journal files are automatically
>> owned by them
>
> This sounds like it has the potential that journal files suddenly
> beomce writable by a rando
On Wednesday 2012-01-25 02:02, Lennart Poettering wrote:
>
>People have been asking us to maintain a NEWS file for systemd. We have
>now added that:
>http://cgit.freedesktop.org/systemd/systemd/plain/NEWS
>I have included all news from the previous release v38 there, please
>have a look.
>[v39]
>
24 matches
Mail list logo
