On Tue, Mar 06, 2018 at 11:26:19PM +, Jonathan de Boyne Pollard wrote:
> Greg Wooledge:
>
> > Wheezy used sysvinit and related pacakges, not systemd. Jessie does have
> > the file-hierarchy(7) man page that Jonathan mentioned.
> >
> Debian 7 had systemd, and the sharp-eyed who read the URL wi
Jonathan de Boyne Pollard wrote:
>> Wheezy used sysvinit and related pacakges, not systemd. Jessie does
>> have the file-hierarchy(7) man page that Jonathan mentioned.
>>
> Debian 7 had systemd, and the sharp-eyed who read the URL will have
> noticed that I pointed to the Debian 7 version of that
On Sat, Mar 03, 2018 at 12:09:54PM -0500, Gene Heskett wrote:
> On Saturday 03 March 2018 11:14:34 Jonathan de Boyne Pollard wrote:
> > Gene Heskett:
> > > Didn't anyone think of the stuff that runs as a user?
> >
> > They did. They gave you a /run/user/$UID directory owned by you, and
> > an XDG_
On Saturday 03 March 2018 11:14:34 Jonathan de Boyne Pollard wrote:
> Gene Heskett:
> > Didn't anyone think of the stuff that runs as a user?
>
> They did. They gave you a /run/user/$UID directory owned by you, and
> an XDG_RUNTIME_DIR environment variable whose value points to it that
> you use
Dave Sherohman:
Or should I be going about this in a completely different manner?
Yes.
[Service]
Type=simple
User=starman
RuntimeDirectory=starman
And simply do not use the --pid and --daemonize options in the first
place. You are using a service manager that tracks child processes and
Sven Hartge writes:
> Mart van de Wege wrote:
>
>> Eh. It's in the docs. /run is for runtime generated, ephemeral units
>> and other files.
>
>> What stumped me at first is that /etc has priority over /run
>
> This is because /etc is designed to override (or amend) anything from
> the system, ei
Mart van de Wege wrote:
> Eh. It's in the docs. /run is for runtime generated, ephemeral units
> and other files.
> What stumped me at first is that /etc has priority over /run
This is because /etc is designed to override (or amend) anything from
the system, either static from (/usr)/lib/system
On Tue 27 Feb 2018 at 20:56:29 (+0100), Martin S. Weber wrote:
> On 2018-02-27 13:29:09, David Wright wrote:
> > On Tue 27 Feb 2018 at 19:20:09 (+0100), Martin S. Weber wrote:
> > > (...)
> > > You're not exactly supposed to call systemd-tmpfiles yourself.
> > > systemd-tmpfiles(8) documents the sy
"Martin S. Weber" writes:
> On 2018-02-27 12:46:46, Gene Heskett wrote:
>> On Tuesday 27 February 2018 06:46:50 Martin S. Weber wrote:
>>
>> > On 2018-02-27 05:03:15, Dave Sherohman wrote:
>> > > (...)
>> > > So, is there somewhere that /run is initially populated from,
>> > > (...)
>> >
>> > ma
On 2018-02-27 13:29:09, David Wright wrote:
> On Tue 27 Feb 2018 at 19:20:09 (+0100), Martin S. Weber wrote:
> > (...)
> > You're not exactly supposed to call systemd-tmpfiles yourself.
> > systemd-tmpfiles(8) documents the systemd services that call
> > systemd-tmpfiles(8).
> > During configurati
On Tue 27 Feb 2018 at 19:20:09 (+0100), Martin S. Weber wrote:
> On 2018-02-27 12:46:46, Gene Heskett wrote:
> > On Tuesday 27 February 2018 06:46:50 Martin S. Weber wrote:
> >
> > > On 2018-02-27 05:03:15, Dave Sherohman wrote:
> > > > (...)
> > > > So, is there somewhere that /run is initially p
Don Armstrong wrote:
> Stuff that runs as a user should use that user's home directory. [I have
> a ~/var/ for this purpose, but other things use environmental variables
> or ~/.something/foopid or similar.]
$HOME/.cache/foobar would be the (current) canonical place, I think.
S°
--
Sigmentati
Martin S. Weber wrote:
> In which of the three, /{etc,run,usr/lib}/tmpfiles.d ? According to
> systemdese,
> the distribution files belong in /usr/lib/ (check the directory, I believe you
> won't find it empty), administrator adjustments in /etc (so no surprise a
> vanilla install doesn't have t
On 2018-02-27 13:40 -0500, Greg Wooledge wrote:
> On Tue, Feb 27, 2018 at 01:38:08PM -0500, Gene Heskett wrote:
>> No /run is indeed a link to /var/run, whish is real, so we're good there.
>> Being sorta forced to learn newer stuff after half a decade on nice
>> stable wheezy has spoilt me.
>
>
On Tuesday 27 February 2018 13:40:34 Greg Wooledge wrote:
> ls -ld /var/run /run
ls -ld /var/run /run
drwxr-xr-x 23 root root 980 Feb 27 07:43 /run
lrwxrwxrwx 1 root root 4 Oct 28 12:46 /var/run -> /run
--
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap,
On Tue, Feb 27, 2018 at 01:38:08PM -0500, Gene Heskett wrote:
> No /run is indeed a link to /var/run, whish is real, so we're good there.
> Being sorta forced to learn newer stuff after half a decade on nice
> stable wheezy has spoilt me.
Even on wheezy, that is not normal.
ebase@ebase-adm:~$ c
On Tuesday 27 February 2018 13:20:09 Martin S. Weber wrote:
> On 2018-02-27 12:46:46, Gene Heskett wrote:
> > On Tuesday 27 February 2018 06:46:50 Martin S. Weber wrote:
> > > On 2018-02-27 05:03:15, Dave Sherohman wrote:
> > > > (...)
> > > > So, is there somewhere that /run is initially populate
On Tuesday 27 February 2018 13:13:34 Don Armstrong wrote:
> On Tue, 27 Feb 2018, Gene Heskett wrote:
> > Just curious Sven. Why was this not supplied as a manpage or
> > something, as far back as wheezy?
>
> It's pretty common knowledge that initscripts and systemd units which
> don't run as root
On 2018-02-27 12:46:46, Gene Heskett wrote:
> On Tuesday 27 February 2018 06:46:50 Martin S. Weber wrote:
>
> > On 2018-02-27 05:03:15, Dave Sherohman wrote:
> > > (...)
> > > So, is there somewhere that /run is initially populated from,
> > > (...)
> >
> > man 5 tmpfiles.d, see also its SEE ALSO.
On Tue, 27 Feb 2018, Gene Heskett wrote:
> Just curious Sven. Why was this not supplied as a manpage or
> something, as far back as wheezy?
It's pretty common knowledge that initscripts and systemd units which
don't run as root have to create temporary directories in /run to track
their pid files
On Tuesday 27 February 2018 06:46:50 Martin S. Weber wrote:
> On 2018-02-27 05:03:15, Dave Sherohman wrote:
> > (...)
> > So, is there somewhere that /run is initially populated from,
> > (...)
>
> man 5 tmpfiles.d, see also its SEE ALSO.
>
> Regards,
> -Martin
Apparently new with jessie. But nei
On Tuesday 27 February 2018 06:45:36 Sven Hartge wrote:
> Dave Sherohman wrote:
> > I've just made my first foray into creating systemd service files,
> > and, although I got them to work with manual startup, they failed
> > miserably on reboot. A short investigation revealed that this is
> > be
On Tuesday 27 February 2018 06:03:15 Dave Sherohman wrote:
> I've just made my first foray into creating systemd service files,
> and, although I got them to work with manual startup, they failed
> miserably on reboot. A short investigation revealed that this is
> because /var/run is not persiste
Thanks! That was just what I needed.
On Tue, Feb 27, 2018 at 12:46:50PM +0100, Martin S. Weber wrote:
> On 2018-02-27 05:03:15, Dave Sherohman wrote:
> > (...)
> > So, is there somewhere that /run is initially populated from,
> > (...)
>
> man 5 tmpfiles.d, see also its SEE ALSO.
>
> Regards,
On 2018-02-27 05:03:15, Dave Sherohman wrote:
> (...)
> So, is there somewhere that /run is initially populated from,
> (...)
man 5 tmpfiles.d, see also its SEE ALSO.
Regards,
-Martin
Dave Sherohman wrote:
> I've just made my first foray into creating systemd service files,
> and, although I got them to work with manual startup, they failed
> miserably on reboot. A short investigation revealed that this is
> because /var/run is not persistent across reboots. (It's a link to
26 matches
Mail list logo