On Thu, 25 Oct 2018 00:26:11 +0200
KatolaZ wrote:
> > What's the best way for me to get a Ceres qcow2 as to work on it in
> > a qemu VM?
> >
>
> Just wait for a few hours, since we are solving an issue with
> util-linux on ceres. Will keep you posted.
Cool. I can't work on anything til
On Wed, 24 Oct 2018 11:08:14 -1000
Joel Roth wrote:
> Hi Steve,
>
> In order to facilitate users experimenting with
> different init systems, and avoid conflicting when switching
> from one to another, how about giving runit its own
> directory, for example /etc/service/runit ?
Excellent
I like the idea of logs being in /var/log by default.
But it would be great if this was modular so that we could disable this default
behaviour, or even do without a logger package installed. So perhaps a switch
to change this default behaviour, so that the logger is just a recommended
On Wed, 24 Oct 2018 18:05:54 -0400, Steve wrote in message
<20181024180554.4f657...@mydesk.domain.cxm>:
> On Wed, 24 Oct 2018 07:31:04 +0200
> "J. Fahrner" wrote:
>
>
> > One wish: please use /bin/sh (dash) for the shell, don't use bash.
> > Bash has a lot more overhead because it is
On Wed, Oct 24, 2018 at 06:09:38PM -0400, Steve Litt wrote:
> On Wed, 24 Oct 2018 09:40:45 +0200
> KatolaZ wrote:
>
> > On Tue, Oct 23, 2018 at 06:58:32PM -0400, Steve Litt wrote:
> > > Hi all,
> > >
> > > I'm about to start adapting runscripts to Devuan ASCII. Many/most
> > > daemons do log
On Wed, 24 Oct 2018 11:42:36 +0200
Didier Kryn wrote:
> I can't see how to do better than logger. The only limitation is
> inherent to the very principle of redirecting stderr: the level is
> the same for all messages because it is passed in the logger command
> line. Instead, a daemon
On Wed, 24 Oct 2018 09:40:45 +0200
KatolaZ wrote:
> On Tue, Oct 23, 2018 at 06:58:32PM -0400, Steve Litt wrote:
> > Hi all,
> >
> > I'm about to start adapting runscripts to Devuan ASCII. Many/most
> > daemons do log messages themselves, but for the ones that don't,
> > I'll be using logger to
On Wed, 24 Oct 2018 07:31:04 +0200
"J. Fahrner" wrote:
> One wish: please use /bin/sh (dash) for the shell, don't use bash.
> Bash has a lot more overhead because it is optimized for interactive
> usage. Many developers don't mind about that and always use bash,
> even for simple start scripts
On Sun, Oct 21, 2018 at 11:19:52AM -0400, Steve Litt wrote:
> Hi all,
>
> The runit (or daemontools or s6) service directory is the directory
> which is scanned for symlinks of runit directories. The Debian runit
> package sets it to /etc/service, the Void package sets it
> to /var/service, and
On 10/24/2018 04:21 AM, Olaf Meeuwissen wrote:
Hi,
Jimmy Johnson writes:
On 10/23/18 3:58 PM, Steve Litt wrote:
using logger to capture stdout and stderr
Steve, I found this:
https://unix.stackexchange.com/questions/124455/linux-how-to-redirect-stdout-stderr-to-logger
What software do I
Le 24/10/2018 à 13:34, Olaf Meeuwissen a écrit :
Of these, rsyslog is installed by default, at least on ascii. If you
could assume rsyslog is always installed, binding the daemon's stdout
and stderr to /dev/log would work fine too.
Not that simple. There's the risk of several processes
On Wed, Oct 24, 2018 at 11:51:07AM +0200, Evilham wrote:
[cut]
>
> I'll just add that when I use runit, I use svlogd. The main reason for
> this being that it is guaranteed to just do the right thing with the
> signals sent by sv and it is flexible enough.
>
> That being said, logger probably
On Wed, Oct 24, 2018 at 08:34:19PM +0900, Olaf Meeuwissen wrote:
[cut]
> >
> > If a daemon is not doing its syslog proper calls, redirecting the
> > stdout and stderr to logger could make sense (but a deamon is normally
> > expected to close stdout and stderr as soon as it is spawned, and use
>
Hi,
KatolaZ writes:
> On Tue, Oct 23, 2018 at 12:32:54PM -0400, Steve Litt wrote:
>
> [cut]
>
>> Ahh, the preceding explains why G. Pape says runit level logs are
>> required on *some* daemons, but not others. If the daemon already
>> performs meaningful syslog() calls, there's no reason for
Hi,
Jimmy Johnson writes:
> On 10/23/18 3:58 PM, Steve Litt wrote:
>> using logger to capture stdout and stderr
>
> Steve, I found this:
>
> https://unix.stackexchange.com/questions/124455/linux-how-to-redirect-stdout-stderr-to-logger
>
> What software do I need to install to follow you?
Hi,
Stephan Seitz writes:
> On Di, Okt 23, 2018 at 08:16:51 -0400, Hendrik Boom wrote:
>>On Tue, Oct 23, 2018 at 08:27:25PM +0900, Olaf Meeuwissen wrote:
>>> Make that: "there *was* a command, chkconfig:"
>>>
>>> It's no longer present in Debian stable (stretch) and later. You can
>>> still
Le 23/10/2018 à 19:27, Steve Litt a écrit :
Vim or Emacs. You can only have one.
Perl, Python, Ruby or Lua. You can only have one.
Mutt or Thunderbird. You can only have one.
Sysvinit, runit, s6, perp or Epoch. You can only have one.
kernel, can you have two?
fstab, can you have
I think this is desired only if you want to enable both rc init
scripts and runit scripts on the same system, which, in my opinion is
not a sane configuration.
"Sane configuration."
Have you been talking to my psychiatrist again? I was involuntarily
committed in 2009 for running
Am 24/10/2018 um 0:58 schrieb Steve Litt:
> Hi all,
>
> I'm about to start adapting runscripts to Devuan ASCII. Many/most
> daemons do log messages themselves, but for the ones that don't, I'll
> be using logger to capture stdout and stderr and put them in the logs.
>
> If anybody has an
Le 23/10/2018 à 18:32, Steve Litt a écrit :
On Tue, 23 Oct 2018 11:06:52 +0200
Didier Kryn wrote:
Logger is a way to redirect to syslog one of the output paths of
an application, by the mean of a pipe, or for a script to send such
messages. Logger reads messages and sends them by
On Wed, Oct 24, 2018 at 10:09:15AM +0200, Edward Bartolo wrote:
> On 24/10/2018, KatolaZ wrote:
> > On Wed, Oct 24, 2018 at 08:38:59AM +0200, Edward Bartolo wrote:
> >> This smells bad, really bad, I dare say, like a putrifying animal. Is
> >> the difficulty to keep up with startup scripts so
On 10/24/18 6:46 AM, Lars Noodén wrote:
> Using the devuan_ascii_2.0.0_amd64_dvd-1.iso image from a USB stick I
> consistently get the error:
>
> [!] Detect and mount CD-ROM
> Error reading Release file
> The CD-ROM does not seem to contain a valid 'Release' file,
> or
On 24/10/2018, KatolaZ wrote:
> On Wed, Oct 24, 2018 at 08:38:59AM +0200, Edward Bartolo wrote:
>> This smells bad, really bad, I dare say, like a putrifying animal. Is
>> the difficulty to keep up with startup scripts so great that Devuan
>> will have to bow its head to using a single supported
On Tue, Oct 23, 2018 at 06:58:32PM -0400, Steve Litt wrote:
> Hi all,
>
> I'm about to start adapting runscripts to Devuan ASCII. Many/most
> daemons do log messages themselves, but for the ones that don't, I'll
> be using logger to capture stdout and stderr and put them in the logs.
>
> If
On Wed, Oct 24, 2018 at 08:38:59AM +0200, Edward Bartolo wrote:
> This smells bad, really bad, I dare say, like a putrifying animal. Is
> the difficulty to keep up with startup scripts so great that Devuan
> will have to bow its head to using a single supported init? This
> reminds me of systemd.
This smells bad, really bad, I dare say, like a putrifying animal. Is
the difficulty to keep up with startup scripts so great that Devuan
will have to bow its head to using a single supported init? This
reminds me of systemd. The excuse was, that Debian did not have enough
man-power to keep using
On 10/24/2018 12:58 AM, Steve Litt wrote:
Hi all,
I'm about to start adapting runscripts to Devuan ASCII. Many/most
daemons do log messages themselves, but for the ones that don't, I'll
be using logger to capture stdout and stderr and put them in the logs.
If anybody has an objection to this,
27 matches
Mail list logo
