des file system access. Both read and write. Typically for
> VFAT. Yeah, a boot loader should not modify the files it is itself
> loaded from and also keep writes generally at a minimum, but counting
> boots is generally the absolute minimum necessary, and can be
> imple
https://systemd.io/ROOT_STORAGE_DAEMONS/
--
Alexander E. Patrakov
CV: http://pc.cd/PLz7
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
arriving at the above.
>
> I assume users want their login passphrase to use local characters.
That's just an assumption, with no data presented to back it up.
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
27;t need to be protected after all, everbody should have the
>same files there anyway, it's $HOME that needs protection.
>
It is still hard (due to the old, now expired, self-embargo) to buy any PC
with a TPM in Russia.
--
Alexander E. Patrakov
_
stinct ones. Being an access point helps, because
one knows that there are no bridges on the far end, i.e. all incoming
packets have Station = Source, and all outgoing packets except
multicast have Station = Destination.
To sidestep this limitation, use something like parprouted instea
nation, the filesystem will be always dirty (i.e.: false
positive), but we can probably manage it with another flag in grubenv.
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
22.05.2016 13:33, Alexander E. Patrakov пишет:
22.05.2016 03:51, Zbigniew Jędrzejewski-Szmek пишет:
Hi,
systemd v230 has been tagged. Enjoy!
CHANGES WITH 230:
* Framebuffer devices (/dev/fb*) and 3D printers and scanners
(devices tagged with ID_MAKER_TOOL) are now
n goals of Wayland,
and this change breaks it.
So, unless one of Wayland developers confirms that they are OK with it,
please revert it and ask for a CVE.
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop
read or process per connection.
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
you actually use the owncloud mount?
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
P.S. Under Windows 7, if the dock station is configured to be used for
additional outputs only, it handles both docking and undocking without a
reboot.
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.
ted by
systemd). In fact, they explicitly disable SysV compatibility in systemd:
# disable sysv compatibility
--with-sysvinit-path=
--with-sysvrcnd-path=
--
Alexander E. Patrakov
___
systemd-devel maili
new or disappearing interfaces
and addresses.
The real problem here is with non-C languages. E.g. node.js, Java,
Python 2.7 and even Go still have absolutely no support for IP_FREEBIND.
--
Alexander E. Patrakov
___
systemd-devel mailin
_begin(pkt)) != 1) {
verbose(VERB_QUERY, "request wrong nr qd=%d",
LDNS_QDCOUNT(sldns_buffer_begin(pkt)));
return LDNS_RCODE_FORMERR;
}
--
Alexander E. Patrakov
___
systemd-devel mailin
a part of odhcpd, which is used in OpenWRT.
https://github.com/sbyx/odhcpd
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
27;t get the lock?
Shouldn't it rather be retried?
What is the supposed recovery here?
Cheers,
Hannes
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
imple wrapper that is able to execute EFI binaries and only
them. Would it be feasible to convert tboot into an EFI binary instead,
and measure/validate it as such, using the API provided by UEFI for that?
--
Alexander E. Patrakov
___
systemd-devel mailing
27.10.2014 22:13, Lennart Poettering wrote:
On Mon, 27.10.14 21:57, Alexander E. Patrakov (patra...@gmail.com) wrote:
27.10.2014 21:49, Lennart Poettering wrote:
On Mon, 27.10.14 21:46, Alexander E. Patrakov (patra...@gmail.com) wrote:
Some time ago, I have complained that some boots are
27.10.2014 22:28, Lennart Poettering wrote:
On Mon, 27.10.14 22:22, Alexander E. Patrakov (patra...@gmail.com) wrote:
Thanks for the pointer. It is good to know that the information is available
in the kernel.
Unfortunately, it is not possible to run the lslocks program manually or see
the
27.10.2014 22:13, Lennart Poettering wrote:
On Mon, 27.10.14 21:57, Alexander E. Patrakov (patra...@gmail.com) wrote:
27.10.2014 21:49, Lennart Poettering wrote:
On Mon, 27.10.14 21:46, Alexander E. Patrakov (patra...@gmail.com) wrote:
Some time ago, I have complained that some boots are
27.10.2014 21:49, Lennart Poettering wrote:
On Mon, 27.10.14 21:46, Alexander E. Patrakov (patra...@gmail.com) wrote:
Some time ago, I have complained that some boots are unsuccessful, because
the /dev/disk/by-id/ata-OCZ-VECTOR_OCZ-Z5CB4KC20X0ZG7F8-part2 symlink (which
should point to /dev
v/sda and interferes with udev event
handling?
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
information about stuck process
Nitpick: this only works only if the "stuck modprobe" bug is 100%
reproducible. Which is not a given. So it is better to collect as much
information about the bug when it is noticed by systemd.
--
Alexander E
h = '/devices/platform/uml-blkdev.1/block/ubdb/ubdb3'
So here the udev coldplug triggers the kernel kobject_uevent for 'ubdb3'.
I don't understand why the systemd unit doesn't change to PLUGGED here! It
should?! Or shouldn't it?
Imho the problem is not specifi
ld an admin react to that log message? I'm fine with it being at
the debug priority, but I am not the person who makes decisions here.
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedeskto
his prevention of loading other drivers is the
thing that slows down the boot.
Second, I am going to XDC2014, LinuxCon Europe and Plumbers. I will take
my laptop with me, feel free to see the situation firsthand or try
debugging patches.
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
10.09.2014 12:58, Tom Gundersen пишет:
On Wed, Sep 10, 2014 at 8:53 AM, Alexander E. Patrakov
wrote:
10.09.2014 12:46, Tom Gundersen пишет:
On Tue, Sep 9, 2014 at 10:45 PM, Luis R. Rodriguez
wrote:
On Tue, Sep 9, 2014 at 12:35 PM, James Bottomley
wrote:
On Tue, 2014-09-09 at 12:16
after
kernel commit 786235ee (November 2013), right?
No. The pata-marvell (or rather libata in general) problem existed
before that.
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.
async-signal safety issues. They use fork quite non-trivially for
background saving of their database from memory to disk.
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/lis
is skipped (and this also means symlinks are
not created). But then there should be an "Unable to flock" debug
message in "journalctl -b -p debug", and it doesn't exist. So it must be
something else. Any other ideas?
--
Alexander E. Patrakov
+ cat /lib/dracut/dracut-
to get a size of blockdev was zero although zram0 has right size
by 2.
The reason is zram didn't revalidate disk after changing capacity
so that size of blockdev's inode is not uptodate until all of file is close.
This patch should fix the problem.
Reported-by: Alexander E. Patrakov
in dmesg.
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
ives/systemd-devel/2014-June/019838.html :
it breaks a (mis-?)documented way to integrate zram swap and systemd.
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
10.06.2014 00:57, Reindl Harald wrote:
Am 09.06.2014 20:45, schrieb Alexander E. Patrakov:
10.06.2014 00:04, Reindl Harald wrote:
Am 09.06.2014 17:05, schrieb Colin Guthrie:
'Twas brillig, and Reindl Harald at 08/06/14 13:59 did gyre and gimble:
"touch /forcefsck" lead
b file. If it has "0 0" as the last two
fields, then, of course, systemd will not call fsck. If there are
different numbers there, sure, let's debug.
Also, now the entity that is supposed to check your root filesystem is
dracut. Are you using it? Does the problem go away if you
the fd to /dev/zram0
open. I could not trace by reading kernel sources why this fails to
change the disk size, but this failure somehow feels logical. I should
just stop setting the "disksize" attribute from an udev rule.
--
Alexander E. Patrakov
___
09.06.2014 20:11, Kay Sievers wrote:
On Mon, Jun 9, 2014 at 4:02 PM, Alexander E. Patrakov
wrote:
09.06.2014 19:26, Kai Krakow wrote:
Alexander E. Patrakov schrieb:
I have upgraded systemd from 212 to 213 on two my Gentoo boxes, and see
the same regression here: zram swap space does not
09.06.2014 19:26, Kai Krakow wrote:
Alexander E. Patrakov schrieb:
I have upgraded systemd from 212 to 213 on two my Gentoo boxes, and see
the same regression here: zram swap space does not get activated. It
looks like systemd tries to activate swap before the RUN+=mkswap part of
the udev
v/zram2 noneswappri=10,discard 0 0
/dev/zram3 none swappri=10,discard 0 0
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
22.05.2014 14:13, Tom Gundersen wrote:
On Thu, May 22, 2014 at 10:00 AM, Alexander E. Patrakov
wrote:
The code touched by commit 9f43a07f1 is possibly buggy. Here is why I think
so.
The new lines added are:
log_full(errno == ENOENT ? LOG_DEBUG : LOG_ERR, "Failed to open
configuration
don't understand why errno in the second line is the original
errno. I.e. why log_full() can't clobber the errno with some other error
that happens while logging.
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-de
is:
https://developer.apple.com/library/mac/documentation/MacOSX/Conceptual/BPSystemStartup/Chapters/CreatingLaunchdJobs.html
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
belongs to a foreign process. Commonly, some kind of file locking
is employed to implement this logic.
I guess that the text needs to be clarified, as currently it is a source
of long-living locks on PID-files, with the associated vulnerabilities.
--
Alexander E. Patrakov
___
distro on it.
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
02.02.2014 20:18, "Jóhann B. Guðmundsson" wrote:
On 02/02/2014 01:39 PM, Alexander E. Patrakov wrote:
The patch is obviously harmless. However, I am not convinced that it
is needed, because in my setup (without this patch) there are no links
in /dev/disk pointing to any zram devic
ated
by systemd.
See
http://lists.freedesktop.org/archives/systemd-devel/2014-February/016614.html
for my configuration files.
One patch that would be useful, however, is to make systemd say "this
system cannot hibernate" if all swap devices are zrams.
--
Alexander E. Patr
swappri=10,discard 0 0
Note that "discard" is essential here (and not mentioned in the Gentoo
wiki) so that zram returns once-used compressed swap to the system.
$ cat /etc/modprobe.d/zram.conf
options zram num_devices=4
$ cat /etc/modules-load.d/zram.conf
zram
--
2013/11/18 Sergey Ptashnick <0comff...@inbox.ru>:
> On 17.11.2013 16:34, Alexander E. Patrakov wrote:
>> You translate "host name" as "имя компьютера", both GDM and KDM translators
>> use "имя узла".
>
> In this case, IMHO, evidence and int
slators use the word "аутентификация", KDM translators
are inconsistent (use both terms).
As for "session" (found in the catalog file), you both use the term "сеанс",
which is good.
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
c/login/org.freedesktop.login1.policy.in.h:21
msgid "Allow attaching devices to seats"
msgstr "Разрешить подключение устройств к терминалу"
Is there any prior art for translating "seat" as "терминал"? Won't
that clash with "tty" at some
s for the translation itself, from my own viewpoint, it is not good
enough to be a final version, but good enough to be commited in a
disabled state so that others can improve it. It is not a problem that
we can't make a perfect translation in just one commit.
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
2013/11/14 Juliette Tux :
> On 14 November 2013 19:10, Alexander E. Patrakov wrote:
>> I have never seen "pretty" translated as "чудесный" in such context
>> (where the meaning is "descriptive, meaningful"). Could you please
>> show some prio
лючателя закрытия крышки"
I think it's an English-only idiom to talk about a "switch" here. So
no "переключателя".
> +#: ../src/timedate/org.freedesktop.timedate1.policy.in.h:7
> +msgid "Turn network time synchronization on or off"
> +msgstr "Включить/выключить синхронизацию с сетевым протоколом времени"
You don't synchronize with a protocol. Maybe: "Включить/выключить
синхронизацию времени по сети"?
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
NeilBrown пишет:
On Wed, 13 Nov 2013 22:11:27 +0600 "Alexander E. Patrakov"
wrote:
2013/11/13 NeilBrown :
On Tue, 12 Nov 2013 19:01:49 +0400 Andrey Borzenkov
wrote:
Something like
mdadm-last-resort@.timer
[Timer]
OnCalendar=+5s
mdadm-last-resort@.service
[Service]
Ty
2013/11/14 Colin Guthrie :
> What kernel are you using out of interest?
This kernel is a git snapshot between 3.12.0-rc2 and -rc3. Compiled on Gentoo.
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
h
2013/11/13 Alexander E. Patrakov :
> 2013/11/13 Colin Guthrie :
>> What about if you generate it with the keyboard plugged in? It should
>> include the usbhid module then, but does it actually work?
>
> Will try a bit later, but I suspect this is the wrong direction of
is the most
frequent reason for USB keyboards and mice to misbehave - the host
just turns them off mistakenly. So
/lib/udev/rules.d/42-usb-hid-pm.rules does look relevant.
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.free
2013/11/13 Colin Guthrie :
> 'Twas brillig, and Alexander E. Patrakov at 13/11/13 16:49 did gyre and
> gimble:
>> 2013/11/13 Alexander E. Patrakov :
>>> Colin Guthrie wrote:
>>>>
>>>> Hi,
>>>>
>>>> In this bug report ht
2013/11/13 Alexander E. Patrakov :
> Colin Guthrie wrote:
>>
>> Hi,
>>
>> In this bug report https://bugs.mageia.org/show_bug.cgi?id=11645 a user is
>> unable to enter their encrypted root password via a wireless keyboard
>> connected with a Logitech, Inc. U
gt;>
>> [Service]
>> Type=oneshot
>> ExecStart=/sbin/mdadm -IRs %n
>>
>> udev rule
>>
>> ... SYSTEMD_WANTS=mdadm-last-resort@$ENV{SOMETHING_UNIQUE}.timer
>>
>
> Thanks. This certainly looks interesting and might be part of a solution.
> However it gets the timeout test backwards.
>
> I don't want to set the timeout when the array starts to appear. I want to
> set the time out when someone wants to use the array.
> If no-one is waiting for the array device, then there is no point forcing it.
>
> That's why I want to plug into the timeout that systemd already has.
>
> Maybe that requirement isn't really necessary though. I'll experiment with
> your approach.
It is useless to even try to plug into the existing systemd timeout,
for a very simple reason. in the setups where your RAID array is not
on the top of the storage device hierarchy, systemd does not know that
it wants your RAID array to appear.
So the statement "If no-one is waiting for the array device, then
there is no point forcing it" is false, because there is no way to
know that no-one is waiting.
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
validate the bug (for the LUKS-password case) later today on my laptop.
The keyboard does work on my desktop, but there's no initramfs there.
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
kmod.
4. The LT_INIT macro has a way to disable the build of static
libraries by default (but the user who runs the configure script can
override this default), and systemd does that.
5. This macro does not have a way to forcibly disable the build of
static libraries.
(5) is a bug in libtool. There is nothing systemd can do about it.
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
them in the path)
* Applicability to both x86 and non-x86 machines
* Being a cross-distribution standard
* Easiness to opt out of the scheme
i.e. imagine that you are writing a US patent, don't be afraid of
essentially duplicate entries.
--
Alexander E. Patrakov
___
2013/1/8 Bryan Kadzban :
> I *suppose* that might be because pkg-config or some equivalent fixes it
> up somehow, pointing to the .la files directly. Or maybe -L affects
> this somehow.
The -L option does have an effect on this.
--
Alexander E.
n.org/cgi-bin/bugreport.cgi?bug=655450
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
eth1=WAn as example, the benefit of such
> scripts is that they can be easily adopted to a new but compareable
> setup and basic rules are always the same
You can achieve the same by manually writing the equivalent of the
persistent rules by hand, just don't name the rena
rd is inserted into the same slot as
the failed one, the name won't change. And in virtual machines
biosdevname deactivates itself automatically.
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
restart means in systemd world. What you described is just a
nice way to do a reload. However, as the main pid changes during this reload,
please be careful - several years ago that would hit an assertion in systemd,
and due to my aziness I have not verified the fix.
--
A
trust the concurrent writer of the file to
behave nicely, mmap-based reading should be outright banned. So please
- either establish and document some kind of trust model between the
reader and the writer, or ban mmap-based reading of non-archived
journal files completely.
--
AC power
while the lid is closed. Would that be OK for you?
--
Alexander E. Patrakov
Sent from Nokia N900
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
ow that a normal "md" raid is able to assemble fake RAIDs perviously
handled by dmraid, could you please try to migrate? Just try to
assemble md raid as usual, obviously without having run dmraid. You'll
get devices like md126_p1 and md126_p2.
-
2012/8/21 Alexander E. Patrakov :
> 2012/8/21 Lennart Poettering :
>> On Sat, 18.08.12 16:04, David Strauss (da...@davidstrauss.net) wrote:
>>> Additionally, socket activation could get rather interesting
>>> capability if there were a middle-ground between single pro
is dynamically. This is supposed to be an
option configured statically by the sysadmin via a configuration file
(a service file?), just like the ServerLimit and MaxClients apache2
config directives. And the whole things looks very much like apache2
preform MPM.
--
Alexander E. Patra
ed screens.
This is not exactly a theoretical question. While I could not
reproduce this race using a RAID0 setup made from two Samsung SATA-III
SSDs, it does trigger reliably (even with an Intel card) if one puts
the entire system into an initramfs and makes the /init ->
usr/bin/systemd sy
efined
policy for getting the "key is not there, panic" error message.
The new asynchronous password agent interface does not help against
races without an easy way to say "this password agent (or even: this
encrypted volume) needs yubikey&
emd to get the effect I want.
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
7;s
switch script (so it doesn't restart bgpd contrary to the
administrator's decision) and not to forget to reenable it later.
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
upport from systemd - just the
ability of the package manager to set a different btrfs root mount
option for next boots.
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
dencies? The "install to btrfs snapshot"
approach would handle this correctly by installing each package as
soon as it gets compiled.
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
the same sequence as above for ext4 and
"make a writable snapshot, install to snapshot, reboot with that
snapshot as root" on btrfs. This, theoretically, has a huge advantage
of being able to work on on source-based distributions like gentoo
(unli
sshd". It may well be the case of
outdated documentation, as I don't see any of the indicated problems
on my desktop or laptop. Still, it would be nice to clarify this
discrepancy in the unit file.
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
2012/6/5 Diego Calleja :
> [resend, for some reason kmail formatted the previous message with html]
>
> On Martes, 5 de junio de 2012 09:50:56 Alexander E. Patrakov escribió:
>> Result: boot from ext4 takes less than 15 seconds, while boot from
>> btrfs takes 9 minutes (or 5
version of the packet structure or an ioctl that returns the correct
size even under linux32.
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
v2 of the patch is the
necessary evil.
One more thing: the service fails (because wpa_supplicant exits
unsuccessfully) if the hardware rfkill switch is off. But this is not a
regression as compared to the current cituation with OpenRC, so it is not
an objection for the patch. IMHO
t; On Mon, Jul 11, 2011 at 10:13:52PM +, Alexander E. Patrakov wrote:
> > > Henry Gebhardt wrote:
> > >
> > > > --- /dev/null
> > > > +++ b/wpa_supplicant/systemd/wpa_supplicant@.service @@ -0,0 +1,11 @@
> > > > +[Unit]
> > > > +D
supplicant should not start before the interface appears?
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
ts 100 seconds
miredo: "hey teredo server, which IPv6 address should I use?"
kernel sends packet
teredo server replies
So it looks like miredo should reset its timeout when the routing table
changes, and that I have to implement this mysel
restart (but not on stop). It is
not obvious for me how this can work without a new directive.
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
18.01.2011 16:51, Lennart Poettering пишет:
On Tue, 18.01.11 16:41, Alexander E. Patrakov (patra...@gmail.com) wrote:
How is this implemented in detail? Sending SIGINT is async, so at the
time you start the new instance you cannot be sure that the old instance
has stopped listening?
Indeed
18.01.2011 04:14, Lennart Poettering пишет:
On Mon, 10.01.11 15:11, Alexander E. Patrakov (patra...@gmail.com) wrote:
[Unit]
Description=Lighttpd Web Server
After=network.target
[Service]
Type=forking
EnvironmentFile=/etc/conf.d/lighttpd
PIDFile=/var/run/lighttpd.pid
ExecStartPre=/usr/sbin
18.01.2011 04:23, Lennart Poettering wrote:
On Tue, 11.01.11 09:54, Alexander E. Patrakov (patra...@gmail.com) wrote:
instances of lighttpd to coexist for some time. See: after SIGINT,
the old instance does not listen on port 80, but continues servicing
large downloads that are still in
ound" fact is tested, not "the command executed successfully".
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
11.01.2011 19:46, Marius Tolzmann wrote:
hi again..
On 01/11/11 11:51, Alexander E. Patrakov wrote:
If you also want graceful stop, you may want to add:
ExecStop=/bin/kill -INT $MAINPID
but this doesn't work, as lighttpd gets killed immediately. I don't know
why this happens.
le is
bad. It should instead complain to syslog and do nothing with the
running instances of lighttpd and lighttpd-angel.
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
file submission recorded in any mailing list?
Basically, I want some mail to use as a template.
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
it is a better idea to use
sshd.socket +
# s...@.service (i.e. the on-demand spawning version for one instance per
# connection).
--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.
may want to play with it
yourself. To experiment with graceful restarts, you can put some music
in the document root and attempt to download it with wget -O /dev/null
--limit-rate=20k http://127.0.0.1/file.mp3 while restarting lighttpd.
--
Alexander E. Patrakov
__
indeed wrong to
fail the assertion due to it, as it would be a security hole. However,
in my opinion, it is also suboptimal (and maybe even wrong) to continue
executing new commands when it is clear that the main PID no longer
exists although it should - i.e., the service died.
--
Alexander E
10.01.2011 18:57, Mirco Tischler wrote:
This patch should fix it. Can you test it? The problem was that after a
the mainpid exits,
and because there are commands left to execute systemd assumes it
executes an ExecStart
line from a type=oneshot service file. But in this case it executes an
ExecRel
patch_sigchld (m=0x25bb1c0) at
src/manager.c:2011
#9 0x004117e3 in manager_process_signal_fd (m=0x25bb1c0) at
src/manager.c:2186
#10 process_event (m=0x25bb1c0) at src/manager.c:2211
#11 manager_loop (m=0x25bb1c0) at src/manager.c:2345
#12 0x0040a1e5 in main (argc=, argv=optimize
1 - 100 of 101 matches
Mail list logo
