On Sat, 02 Jul 2016 16:48:40 +0300 Kalle Olavi Niemitalo wrote:
> Package: rsyslog
> Version: 8.16.0-1+b4
> Severity: normal
> User: debian-hurd@lists.debian.org
> Usertags: hurd
>
> I get this to /var/log/syslog on each boot:
>
> Jul 2 16:19:36 luuska rsyslogd: [origin software="rsyslogd"
>
Am 29.12.18 um 19:33 schrieb Dmitry Bogatov:
> I propose to re-evaluate this issue. We still call function clean_all()
> three time during boot. By the way, RAMRUN no longer actually used in
> any way:
Since you CCed me, I guess you want my input on something. It's just not
entirely clear what.
Hi Rainer
Am 05.11.18 um 10:43 schrieb Rainer Gerhards:
> Hi,
>
> Rainer from upstream here. Where is the missing lsof causing issues?
> That would probably be the right place to fix. I did a grep over the
> testbench and do not see any place where it is required (tests skip
> via 77 exit code
Am 04.11.18 um 18:48 schrieb Samuel Thibault:
> Additionally, the attached patch is needed since lsof is non available
> on non-linux.
Is lsof not available at all or just provided by a different package?
--
Why is it that all of the instruments seeking intelligent life in the
universe are
Am 07.06.2018 um 13:37 schrieb Samuel Thibault:
> Michael Biebl, le jeu. 07 juin 2018 13:34:48 +0200, a ecrit:
>> Anyway, such patches should best be sent upstream.
>
> We don't have the manpower to chase all upstream bugtrackers and
> whatnot.
Same is true for me. I don't
Am 26.10.2017 um 16:59 schrieb Cyril Brulebois:
> Hi,
>
> Michael Biebl <bi...@debian.org> (2017-10-24):
>> It's actually smaller then the old eject-udeb as I didn't include the
>> gettext translations.
>
> Why? OK this was late and maybe I wasn't clear on IRC, b
Am 27.07.2016 um 16:56 schrieb Steven Chamberlain:
> Hi,
>
> Michael Biebl wrote:
>> Afaics, there weren't any concerns raised by our -hurd@ and -bsd@
>> maintainers so far. If you need more time to evaluate the change, please
>> speak up now. Otherwise I'd ask
tag 830894 - moreinfo
tag 830895 - moreinfo
tag 830901 - moreinfo
thanks
Am 22.07.2016 um 00:30 schrieb Cyril Brulebois:
> No objections from my point of view. Adding -hurd@ and -bsd@ to the loop
> for their information, just in case.
With KiBi's feedback, I'm removing the moreinfo.
Afaics,
On 19.05.2012 23:59, Samuel Thibault wrote:
Hello,
Cyril Brulebois, le Sat 19 May 2012 19:41:56 +0200, a écrit :
(Ewww, long lines)
Oops, sorry, I forgot to reindent after import from the pad.
Samuel Thibault sthiba...@debian.org (19/05/2012):
- We of course aim at tech preview for
Hi Guillem,
On 27.01.2012 10:18, Guillem Jover wrote:
* rsyslog should probably switch to use s-s-d --exec instead (why is
it using --name anyway? that option has always been more unreliable).
Still pending.
Upon your recommendation, I've switched stop() to s-s-d --pidfile
Hi,
Am 06.04.2012 18:15, schrieb Guillem Jover:
On Fri, 2012-04-06 at 10:09:01 +0200, Michael Biebl wrote:
On 27.01.2012 10:18, Guillem Jover wrote:
* rsyslog should probably switch to use s-s-d --exec instead (why is
it using --name anyway? that option has always been more unreliable
Hi,
On 27.01.2012 10:18, Guillem Jover wrote:
On Sat, 2011-12-24 at 05:30:33 +0100, Guillem Jover wrote:
* start-stop-daemon (s-s-d) does not make use of procfs, but its
Hurd --name implementation seems to be buggy in any case. I'll fix
this directly myself.
* s-s-d man page talks
Thanks for all the efforts, but WTH does GNU/hurd not simply #define
PATH_MAX and be done with it. This would solve 90% of the build failures
we have in Debian.
This all looks like a major waste of time to me.
Michael
--
Why is it that all of the instruments seeking intelligent life in the
13 matches
Mail list logo
