Hi,
> i am trying to build a binary debian package consisting of a python
> script, shell scripts and a config file as daemon with either init.d or
> systemd start.
>
> The init.d script gets installed also the systemd file, but both are not
> enabled.
[...]
> In debian/
Dear Tim,
I followed your advise to restucture my stuff exactly like you
suggested.
Putting all files in a structure below source, Makefile,
PACKAGE.install ... everything.
And now it works!
I get init.d and systemd _enabled_ start scripts.
Installing this way I get an error at the target
Dear Darac,
> > The files
> > /etc/init.d/loqitmon
> > /lib/systemd/system/loqitmon.service
> The manpage for dh_installsystemd suggests these files should be under
> debian/. Are they, or are they in etc/init.d and lib/systemd/system?
I have those below debian, this w
On Thu, 2 Mar 2023, Konstantin Kletschke wrote:
In debian/rules is:
#!/usr/bin/make -f
DH_VERBOSE=1
%:
dh $@
clean:
@# Do nothing
build:
@# Do nothing
binary:
mkdir -p debian/loqitmon
mkdir -p debian/loqitmon/usr/
mkdir -p debian/loqitmon/usr/
On 02/03/2023 19:56, Konstantin Kletschke wrote:
Dear debian-user Folks,
i am trying to build a binary debian package consisting of a python
script, shell scripts and a config file as daemon with either init.d or
systemd start.
The init.d script gets installed also the systemd file, but both
Dear debian-user Folks,
i am trying to build a binary debian package consisting of a python
script, shell scripts and a config file as daemon with either init.d or
systemd start.
The init.d script gets installed also the systemd file, but both are not
enabled.
I made a directory loqitmon-1.0
> would be to use a suited nn number (and in fact, if my init.d script
> > would get started at all it won't work because of a missing user as
> > it is started before pam ldap - this are places where I expect problems,
> > not at the attempt to run or not at all).
>
&
On Fri, Oct 25, 2019 at 11:14:22PM +0200, Steffen Dettmer wrote:
[...]
> Not sure if on topic, but I what is needed to guess, it should run the
> scripts in order of their rcX/Snn number? I though the difficulty
> would be to use a suited nn number (and in fact, if my init.d script
&g
Hi,
thanks for your reply.
On Tue, Oct 22, 2019 at 5:45 AM Peter Wiersig wrote:
> Steffen Dettmer writes:
> > So you propose not to use init.d scripts. I usually prefer a simple shell
> > script that is easy to test, systemd is just way to complex.
>
> Like Greg sa
On Mon, Oct 21, 2019 at 9:32 PM Greg Wooledge wrote:
> On Mon, Oct 21, 2019 at 09:26:57PM +0200, Steffen Dettmer wrote:
> > On Mon, Oct 21, 2019 at 3:27 PM Greg Wooledge
> wrote:
> > > This is not correct. Debian's systemd will use init.d scripts in
> > > co
Steffen Dettmer writes:
> So you propose not to use init.d scripts. I usually prefer a simple shell
> script that is easy to test, systemd is just way to complex. But probably
> for Debian you are right, if I understood correctly, newer versions do not
> even support init.d / LSB
On Mon, Oct 21, 2019 at 09:26:57PM +0200, Steffen Dettmer wrote:
> On Mon, Oct 21, 2019 at 3:27 PM Greg Wooledge wrote:
> > This is not correct. Debian's systemd will use init.d scripts in
> > compatibility mode.
>
> Ahh, this sounds good! But how to do that correc
Hi,
thanks for your reply.
On Mon, Oct 21, 2019 at 3:27 PM Greg Wooledge wrote:
> > But probably
> > for Debian you are right, if I understood correctly, newer versions do
> not
> > even support init.d / LSB anymore, so using systemd units seems to be
> > requ
On Mon, Oct 21, 2019 at 12:20:10PM +0200, Steffen Dettmer wrote:
> So you propose not to use init.d scripts. I usually prefer a simple shell
> script that is easy to test, systemd is just way to complex.
An init.d script is approximately 5 to 10 times as complicated as
a systemd unit.
Hi,
thanks for your reply.
On Sun, Oct 20, 2019 at 10:26 PM Peter Wiersig
wrote:
> 5.)
> Instead of init.d scripts create systemd units.
> https://wiki.debian.org/systemd#Creating_or_altering_services
https://freedesktop.org/wiki/Software/systemd/
So you propose not to use init.d s
Hi,
thank you for your reply.
On Fri, Oct 18, 2019 at 3:34 PM Jonas Smedegaard wrote:
> Quoting Steffen Dettmer (2019-10-18 15:17:10)
> > in short: how to use "init.d" scripts on Debian?
>
> In short:
>
> service $SERVICE stop
>
Thanks for the tip. man i
5.)
Instead of init.d scripts create systemd units.
https://wiki.debian.org/systemd#Creating_or_altering_services
https://freedesktop.org/wiki/Software/systemd/
About your gitlab-runner.service failure:
https://wiki.debian.org/systemd#Failed_units
HINT: Extensive debugging information about
Quoting Steffen Dettmer (2019-10-18 15:17:10)
> in short: how to use "init.d" scripts on Debian?
In short:
service $SERVICE stop
service $SERVICE start
service $SERVICE reload
service $SERVICE force-reload
service $SERVICE restart
> in detail:
>
> On one serve
Hi,
in short: how to use "init.d" scripts on Debian?
in detail:
On one server a init.d script with LSB header does not work, at least when
started by command line. I traced down the following:
#1 init.d/script sources /lib/lsb/init-functions
#2 /lib/lsb/init-functions has support
I don't understand the point of this email -- are you advocating for some
change, or to avoid some change?
(I looked at the bug report and skimmed some of the messages -- it seems like
by posting this to the debian-user list you are looking for comments or
support here, but the issue is not c
Thorsten Glaser:
> Just accept that this idea, originating from the systemd people at
Fedora/Freedesktop, is NOT welcome to classical Unix people.
Ahem! We classical Unix people experienced this idea in the late 1980s,
from where it *really* originated, Sun and AT&T.
* https://groups.googl
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will rep
On 2018-10-28 16:58 +, Grzesiek Sójka wrote:
> On 10/28/18 2:10 PM, Sven Joachim wrote:
>> Wouldn't it be better to fix the init system that sets such a bad
>> default PATH? Whatever init system that may be - sysv-rc's
>> /etc/init.d/rc script sets PATH=/sbin:/
On 10/28/18 2:10 PM, Sven Joachim wrote:
Wouldn't it be better to fix the init system that sets such a bad
default PATH? Whatever init system that may be - sysv-rc's
/etc/init.d/rc script sets PATH=/sbin:/usr/sbin:/bin:/usr/bin, so this
should not happen with sysvinit + sysv-rc.
Pl
On 2018-10-28 14:47 +, Grzesiek Sójka wrote:
> On 10/28/18 11:27 AM, Grzesiek Sójka wrote:
>> Hi there,
>>
>> I just upgraded Sid and now I get the following during boot:
>>
>> [] Configuring network interfaces.../etc/init.d/rpcbind: 42:
>> /etc/
On 10/28/18 11:27 AM, Grzesiek Sójka wrote:
Hi there,
I just upgraded Sid and now I get the following during boot:
[] Configuring network interfaces.../etc/init.d/rpcbind: 42:
/etc/init.d/rpcbind: stat: not found
/run/rpcbind not owned by root failed!
Starting NFS common utilities: statd
> If you want to make your daemon interoperate with systemd's status
> mechanism to the extent of having custom status reports, you have to
> modify your daemon to send readiness notification messages through a
> socket to the systemd service manager. That way, not only wil
Looks like systemd does not execute the statements in status) case of the init script
at all, but just checks if the daemon process exists. My '/etc/init.d/ status' did much more, i.e., it checked if the daemon was actually able to
do some real work.
So far I have had no luck in f
On Friday 20 May 2016 18:08:37 Rodary Jacques wrote:
> I read quite a lot of the answers to your post, and I still think there is
> a problem, not linked to the kernel's interface name name. I have a wifi
> interface named *everywhere* wlan0. It isn't found by network-pre.target,
> network-target
I read quite a lot of the answers to your post, and I still think there is a
problem, not
linked to the kernel's interface name name. I have a wifi interface named
*everywhere*
wlan0. It isn't found by network-pre.target, network-target or
networking-service, I
don't know which one. What I k
On 2016-05-18, Gene Heskett wrote:
>> *exactly* those devices tagged as "auto" in /etc/network/interfaces.
>>
>> So that should be the database you're looking for? Try, for starters
>>
>> grep auto /etc/network/interfaces
>
> auto lo eth0 eth1
>
> Its there in the complete interfaces file I just
On Wed 18 May 2016 at 12:32:24 -0500, David Wright wrote:
> On Wed 18 May 2016 at 17:39:45 (+0100), Brian wrote:
> > On Wed 18 May 2016 at 10:44:40 -0500, David Wright wrote:
> >
> > > On Wed 18 May 2016 at 10:56:01 (-0400), Gene Heskett wrote:
> > > >
> > > > auto lo eth0 eth1
> > >
> > > Agre
On Wed 18 May 2016 at 17:39:45 (+0100), Brian wrote:
> On Wed 18 May 2016 at 10:44:40 -0500, David Wright wrote:
>
> > On Wed 18 May 2016 at 10:56:01 (-0400), Gene Heskett wrote:
> > >
> > > auto lo eth0 eth1
> >
> > Agree with Lisi, I've never seen this (though I'm not claiming it's
> > either
On Wed 18 May 2016 at 10:50:23 (+0200), to...@tuxteam.de wrote:
> On Tue, May 17, 2016 at 11:22:29AM -0500, David Wright wrote:
> > On Tue 17 May 2016 at 11:26:28 (-0400), Gene Heskett wrote:
>
> [...]
What was snipped is "I do not see that as a disadvantage, udev can do
that much unwanted damage
On Wed 18 May 2016 at 10:44:40 -0500, David Wright wrote:
> On Wed 18 May 2016 at 10:56:01 (-0400), Gene Heskett wrote:
> >
> > auto lo eth0 eth1
>
> Agree with Lisi, I've never seen this (though I'm not claiming it's
> either wrong or harmful).
It's an ok line. From interfaces(5):
Lines beg
On Wednesday 18 May 2016 16:54:49 Gene Heskett wrote:
> "auto lo eth0"
auto lo
and
auto eth0
now??
Lisi
It may not solve anything, but when rationality seems to fail one has to
resort to magic, and just get the incantation right
Lisi
On 2016-05-16 21:36 +0300, Juha Heinanen wrote:
> When I upgraded one of my wheezy hosts to jessie, I noticed that
>
> /etc/init.d/ status
>
> command stopped working.
>
> Looks like systemd does not execute the statements in status) case of
> the init script at all, but j
On Wednesday 18 May 2016 11:37:59 Lisi Reisz wrote:
> On Wednesday 18 May 2016 16:14:36 Gene Heskett wrote:
> > auto lo eth0 eth1
> >
> > Its there in the complete interfaces file I just posted, and you
> > snipped.
>
> Gene - we have, I think, established that your set-up doesn't work the
> way p
14:34, Mimiko a écrit :
> > > > > On 17.05.2016 15:16, Elimar Riesebieter wrote:
> > > > > > Ask your search engine: "init.d/networking restart is
> > > > > > deprecated"
> > > > >
> > > > > This was the only
On Wednesday 18 May 2016 16:14:36 Gene Heskett wrote:
> auto lo eth0 eth1
>
> Its there in the complete interfaces file I just posted, and you snipped.
Gene - we have, I think, established that your set-up doesn't work the way
predicted.
The one thing that looks very different to me is the stick
n 17.05.2016 15:16, Elimar Riesebieter wrote:
> > > > Ask your search engine: "init.d/networking restart is
> > > > deprecated"
> > >
> > > This was the only tool to fully restart all networking even the
> > > interface thru which connection i
lin [2016-05-17
> > > > 19:09
> >
> > +0200]:
> > > > > Le 17/05/2016 à 14:34, Mimiko a écrit :
> > > > > > On 17.05.2016 15:16, Elimar Riesebieter wrote:
> > > > > > > Ask your search engine: "init.d/networking restart
t; > > > > Ask your search engine: "init.d/networking restart is
> > > > > deprecated"
> > > >
> > > > This was the only tool to fully restart all networking even the
> > > > interface thru which connection is made.
> >
+0200]:
> > > > Le 17/05/2016 à 14:34, Mimiko a écrit :
> > > > > On 17.05.2016 15:16, Elimar Riesebieter wrote:
> > > > > > Ask your search engine: "init.d/networking restart is
> > > > > > deprecated"
> > > &g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, May 18, 2016 at 03:42:27PM +0200, Elimar Riesebieter wrote:
> * Lisi Reisz [2016-05-18 12:31 +0100]:
>
> > On Tuesday 17 May 2016 18:29:36 Elimar Riesebieter wrote:
> [...]
> > > /etc/init.d/networking stop does ifd
On Wednesday 18 May 2016 14:42:27 Elimar Riesebieter wrote:
> * Lisi Reisz [2016-05-18 12:31 +0100]:
> > On Tuesday 17 May 2016 18:29:36 Elimar Riesebieter wrote:
>
> [...]
>
> > > /etc/init.d/networking stop does ifdown -a
> > > /etc/init.d/networking start d
* Lisi Reisz [2016-05-18 12:31 +0100]:
> On Tuesday 17 May 2016 18:29:36 Elimar Riesebieter wrote:
[...]
> > /etc/init.d/networking stop does ifdown -a
> > /etc/init.d/networking start does ifup -a
>
> But
> # ifdown -a; ifup -a
> is much more elegant!!
I would u
On Tuesday 17 May 2016 18:29:36 Elimar Riesebieter wrote:
> * Gilles Mocellin [2016-05-17 19:09 +0200]:
> > Le 17/05/2016 à 14:34, Mimiko a écrit :
> > > On 17.05.2016 15:16, Elimar Riesebieter wrote:
> > > > Ask your search engine: "init.d/networking restart
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, May 17, 2016 at 11:22:29AM -0500, David Wright wrote:
> On Tue 17 May 2016 at 11:26:28 (-0400), Gene Heskett wrote:
[...]
> You don't see any disadvantage to removing the "hotplug stuff".
> Hooray, let's go back to PCs as static boxes. Shut i
On Tuesday 17 May 2016 19:30:06 Lisi Reisz wrote:
> On Tuesday 17 May 2016 23:43:08 Gene Heskett wrote:
> [snip]
>
> If it ain't broke, hit it with a hammer? ;-)
>
> Lisi
Yup, have you got a bigger one my lady?
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soa
On Tuesday 17 May 2016 23:43:08 Gene Heskett wrote:
[snip]
If it ain't broke, hit it with a hammer? ;-)
Lisi
On Tuesday 17 May 2016 15:25:47 Andy Smith wrote:
> Hi Gene,
>
> On Tue, May 17, 2016 at 03:12:45PM -0400, Gene Heskett wrote:
> > Configuring interface eth1=eth1 (inet)
> > run-parts --verbose /etc/network/if-pre-up.d
> > run-parts: executing /etc/network/if-pre-up.d/wireless-tools
> > run-parts:
On Tue 17 May 2016 at 14:51:57 (-0400), Gene Heskett wrote:
> Interesting is that in a man 5 interfaces, it says the gateway address is
> colon delimited. I don't recall ever seeing that since my first install
> in early 1998. Does anyone ever actually read these man pages but me?
Yes, but I h
Hi Gene,
On Tue, May 17, 2016 at 03:12:45PM -0400, Gene Heskett wrote:
> Configuring interface eth1=eth1 (inet)
> run-parts --verbose /etc/network/if-pre-up.d
> run-parts: executing /etc/network/if-pre-up.d/wireless-tools
> run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
> ip addr add
On Tuesday 17 May 2016 13:26:35 Elimar Riesebieter wrote:
> * Gene Heskett [2016-05-17 11:26 -0400]:
>
> [...]
>
> > Because of some rare condition, you make
> > all the other users with a less rare condition suffer?
>
> I was just talking about facts, nothing e
On Tuesday 17 May 2016 13:09:33 Gilles Mocellin wrote:
> Le 17/05/2016 à 14:34, Mimiko a écrit :
> > On 17.05.2016 15:16, Elimar Riesebieter wrote:
> >> Ask your search engine: "init.d/networking restart is deprecated"
> >
> > This was the only tool
On Tue 17 May 2016 at 16:38:52 (+0200), Elimar Riesebieter wrote:
> * Gene Heskett [2016-05-17 09:56 -0400]:
> > On Tuesday 17 May 2016 09:08:55 to...@tuxteam.de wrote:
> [...]
> > > In my opinion, a warning is in order ("this might not be doing
> > > what you think it does"), but deprecated seems
On Tuesday 17 May 2016 12:22:29 David Wright wrote:
> On Tue 17 May 2016 at 11:26:28 (-0400), Gene Heskett wrote:
> > On Tuesday 17 May 2016 10:38:52 Elimar Riesebieter wrote:
> > > * Gene Heskett [2016-05-17 09:56 -0400]:
> > > > On Tuesday 17 May 2016 09:08:55 to...@tuxteam.de wrote:
> > >
> >
* Gilles Mocellin [2016-05-17 19:09 +0200]:
> Le 17/05/2016 à 14:34, Mimiko a écrit :
> > On 17.05.2016 15:16, Elimar Riesebieter wrote:
> > > Ask your search engine: "init.d/networking restart is deprecated"
> >
> > This was the only tool to fully resta
* Gene Heskett [2016-05-17 11:26 -0400]:
[...]
> Because of some rare condition, you make
> all the other users with a less rare condition suffer?
I was just talking about facts, nothing else. If you open
/etc/init.d/networking (ifupdown_0.7.8) in an editor and scroll down
to
Le 17/05/2016 à 14:34, Mimiko a écrit :
On 17.05.2016 15:16, Elimar Riesebieter wrote:
Ask your search engine: "init.d/networking restart is deprecated"
This was the only tool to fully restart all networking even the
interface thru which connection is made.
Are the `ifdown eth
On Tue 17 May 2016 at 11:26:28 (-0400), Gene Heskett wrote:
> On Tuesday 17 May 2016 10:38:52 Elimar Riesebieter wrote:
> > * Gene Heskett [2016-05-17 09:56 -0400]:
> > > On Tuesday 17 May 2016 09:08:55 to...@tuxteam.de wrote:
> > [...]
> > > > In my opinion, a warning is in order ("this might not
On Tuesday 17 May 2016 10:38:52 Elimar Riesebieter wrote:
> * Gene Heskett [2016-05-17 09:56 -0400]:
> > On Tuesday 17 May 2016 09:08:55 to...@tuxteam.de wrote:
>
> [...]
>
> > > In my opinion, a warning is in order ("this might not be doing
> > > what you think it does"), but deprecated seems ex
On Tuesday 17 May 2016 15:38:52 Elimar Riesebieter wrote:
> * Gene Heskett [2016-05-17 09:56 -0400]:
> > On Tuesday 17 May 2016 09:08:55 to...@tuxteam.de wrote:
>
> [...]
>
> > > In my opinion, a warning is in order ("this might not be doing
> > > what you think it does"), but deprecated seems exa
Hi Elimar,
>> On Tuesday 17 May 2016 09:08:55 to...@tuxteam.de wrote:
>>
>[...]
>> > In my opinion, a warning is in order ("this might not be doing what
>> > you think it does"), but deprecated seems exaggerated to me.
>> >
>> > regards
>> >
>> > [1] Schocking Truth! Not everything seen on the I
* Gene Heskett [2016-05-17 09:56 -0400]:
> On Tuesday 17 May 2016 09:08:55 to...@tuxteam.de wrote:
>
[...]
> > In my opinion, a warning is in order ("this might not be doing
> > what you think it does"), but deprecated seems exaggerated to me.
> >
> > regards
> >
> > [1] Schocking Truth! Not eve
On Tuesday 17 May 2016 09:08:55 to...@tuxteam.de wrote:
> On Tue, May 17, 2016 at 02:16:32PM +0200, Elimar Riesebieter wrote:
>
> [...]
>
> > Ask your search engine: "init.d/networking restart is deprecated"
>
> I don't know about yours, but *my* /etc/i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, May 17, 2016 at 03:36:58PM +0200, Elimar Riesebieter wrote:
[...]
> I don't understand why "init.d/networking restart is deprecated" is
> scaring off people? It is a matter of fact! Reading the results will
> give
* to...@tuxteam.de [2016-05-17 15:08 +0200]:
> On Tue, May 17, 2016 at 02:16:32PM +0200, Elimar Riesebieter wrote:
>
> [...]
>
> > Ask your search engine: "init.d/networking restart is deprecated"
>
> I don't know about yours, but *my* /etc/init.d/net
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, May 17, 2016 at 02:16:32PM +0200, Elimar Riesebieter wrote:
[...]
> Ask your search engine: "init.d/networking restart is deprecated"
I don't know about yours, but *my* /etc/init.d/networking is alive
and healthy! More to
+++ _use_systemctl=0
+++ '[' -d /run/systemd/system ']'
+++ '[' -n '' ']'
+++ '[' 20132 -ne 1 ']'
+++ '[' -z '' ']'
+++ '[' -z '' ']'
+++ case $(readlink -f "$0
cket,
> > and ATM it is but the far end of 5 feet of cat5 is laying on the
> > floor.
> >
> > Is it possible to make this init.d/networking script start
> > everything it finds in the interfaces file?
>
> Ask your search engine: "init.d/networking restart is depr
Darac Marjal writes:
> On the face of it, this *should* still work. When you invoke
> "/etc/init.d/example status", you're running the shell script directly -
> that is, without any reference to systemd. Now, I don't remember the
> details, but I seem to recal
On 17.05.2016 15:16, Elimar Riesebieter wrote:
Ask your search engine: "init.d/networking restart is deprecated"
This was the only tool to fully restart all networking even the
interface thru which connection is made.
Are the `ifdown eth & ifup eth` the only option now?
--
Mimiko desu.
On Tuesday 17 May 2016 08:11:50 Peter Ludikovsky wrote:
> In /etc/network/interfaces change
> allow-hotplug eth1
> to
> auto eth1
Blind as a bat, gonna have to get my cateracts fixed as I didn't see
that. I don't have the allow-hotplug line, but the auto line didn't have
eth1, added, wo
tart the second eth1
> stanza in my interfaces file, starting only eth0.
>
> Normally the interface is not even graced with a cat5 in the socket, and
> ATM it is but the far end of 5 feet of cat5 is laying on the floor.
>
> Is it possible to make this init.d/networking script star
t5 is laying on the floor.
>
> Is it possible to make this init.d/networking script start everything it
> finds in the interfaces file?
>
> Cheers, Gene Heskett
>
signature.asc
Description: OpenPGP digital signature
ith a cat5 in the socket, and
ATM it is but the far end of 5 feet of cat5 is laying on the floor.
Is it possible to make this init.d/networking script start everything it
finds in the interfaces file?
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ba
On Mon, May 16, 2016 at 09:36:46PM +0300, Juha Heinanen wrote:
When I upgraded one of my wheezy hosts to jessie, I noticed that
/etc/init.d/ status
command stopped working.
Looks like systemd does not execute the statements in status) case of
the init script at all, but just checks if the
When I upgraded one of my wheezy hosts to jessie, I noticed that
/etc/init.d/ status
command stopped working.
Looks like systemd does not execute the statements in status) case of
the init script at all, but just checks if the daemon process exists.
My '/etc/init.d/ status' did much
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 05/05/2015 12:28 PM, Thomas H. George wrote:
> On Tue, May 05, 2015 at 05:54:53PM +0200, Michael Biebl wrote:
>> Am 05.05.2015 um 17:13 schrieb Thomas H. George:
>>> Entered /etc/init.d/gdm3 start from a root console. Respons
On Tue, May 05, 2015 at 05:54:53PM +0200, Michael Biebl wrote:
> Am 05.05.2015 um 17:13 schrieb Thomas H. George:
> > Entered /etc/init.d/gdm3 start from a root console. Response was to
> > check systemctl status gdm.service and journalctl -xn. A script of the
> > ou
Am 05.05.2015 um 17:13 schrieb Thomas H. George:
> Entered /etc/init.d/gdm3 start from a root console. Response was to
> check systemctl status gdm.service and journalctl -xn. A script of the
> output of these entries:
>
>
> Script started on Tue 05 May 2015 10:58:05 AM ED
On Tue, May 05, 2015 at 11:13:15AM -0400, Thomas H. George wrote:
> Entered /etc/init.d/gdm3 start from a root console. Response was to
> check systemctl status gdm.service and journalctl -xn. A script of the
> output of these entries:
>
>
> Script started on Tue 05 May 20
Entered /etc/init.d/gdm3 start from a root console. Response was to
check systemctl status gdm.service and journalctl -xn. A script of the
output of these entries:
Script started on Tue 05 May 2015 10:58:05 AM EDT
[01;35mZebra:~# [00msystemctl status gdm.service
[1;31m●[0m gdm.service
Andrei POPESCU wrote:
On Vi, 19 sep 14, 13:47:50, Thomas H. George wrote:
My system is Wheezy and I would like to add a script to init.d run a
simple perl program at startup.
...
Can someone give me a simple example script?
/etc/init.d/skeleton
Neat! Never knew that was around...
Hugo
On Vi, 19 sep 14, 13:47:50, Thomas H. George wrote:
> My system is Wheezy and I would like to add a script to init.d run a
> simple perl program at startup.
...
> Can someone give me a simple example script?
/etc/init.d/skeleton
Kind regards,
Andrei
--
http://wiki.d
My system is Wheezy and I would like to add a script to init.d run a
simple perl program at startup.
The scripts in init.d look very different these days, they used to be
numbered so I could make my program run last. I have tried reading the
debian-policy manual and examining some of the
Lisi Reisz a écrit :
> On Sunday 01 September 2013 10:26:22 Erwan David wrote:
>> Et ces règles ne dépendent de rien d'autre ? Par exemple chez moi j'ai
>> une interface tun0 pour un VPN? qui n'existera que si le VPN est lancé...
>
> This is an English language list!
Looks like that post escaped
On Sunday 01 September 2013 10:26:22 Erwan David wrote:
> Le 01/09/2013 11:10, Dominique Asselineau a écrit :
> > François TOURDE wrote on Sun, Sep 01, 2013 at 10:00:55AM +0200
> >
> >> Le 15949ième jour après Epoch,
> >>
> >> Gaëtan PERRIER écrivait:
> >>> Bonsoir,
[snip]
> Et ces règles ne dépend
Le 01/09/2013 11:10, Dominique Asselineau a écrit :
> François TOURDE wrote on Sun, Sep 01, 2013 at 10:00:55AM +0200
>> Le 15949ième jour après Epoch,
>> Gaëtan PERRIER écrivait:
>>
>>> Bonsoir,
>>>
>>> C'est possible quand on est sur un réseau statique mais avec une réseau
>>> en dhcp ça ne me sem
thanks for your help, I solved the problem
Nice.
Just a small reply to notice you that something with your mail client
is wrong: I've received most of your messages replies 4 times.
Not a real problem for me anyway, but for longer discussions it could
be very boring.
Have a good day.
--
T
On Fri, Jan 25, 2013 at 5:16 PM, Benin Technologies
wrote:
>
> Running Debian 6.0.4
>
> Does anybody have an idea why a program wouldn't start at boot, while it's
> init.d script works fine ?
>
> I experience the problem with OpenLDAP 2.4.33, when compiled with b
hi,
thanks for your help, I solved the problem
What I did :
When I start slapd through "/etc/init.d/slapd start", it looks for the
library "/usr/local/lib/libodbc.so.2"
That path is in my LD_LIBRARY_PATH environment variable, so the script
starts fine.
But apparently
e commands I run once Debian is up and running, and
> once I'm already logged in :
>
> # /etc/init.d/slapd start
> Starting OpenLDAP: slapd (just to check that my
> init.d/slapd script works)
>
> # /etc/init.d/slapd stop
> Stopping Op
yes I did
#update-rc.d slapd defaults
Basically, the problem seems to be that
service slapd startDOESN'T WORK, while
/etc/init.d/slapd start WORKS FINE
I know exactly WHERE the problem comes from, but I have no idea how to
fix it
The problem comes from my configur
yes I did
#update-rc.d slapd defaults
Basically, the problem seems to be that
service slapd startDOESN'T WORK, while
/etc/init.d/slapd start WORKS FINE
I know exactly WHERE the problem comes from, but I have no idea how to
fix it
The problem comes from my configur
hi,
thanks for your reply
That's what I thought too, but I don't think it has something to do with
dependencies. Below some commands I run once Debian is up and running,
and once I'm already logged in :
# /etc/init.d/slapd start
Starting OpenLDAP: slapd
hi,
thanks for your reply
That's what I thought too, but it's definitely not that. Below some
commands I run once Debian is up and running, and once I'm already
logged in :
# /etc/init.d/slapd start
Starting OpenLDAP: slapd (just to check that my
init
Le 25.01.2013 23:16, Benin Technologies a écrit :
Hi,
Running Debian 6.0.4
Does anybody have an idea why a program wouldn't start at boot, while
it's init.d script works fine ?
I experience the problem with OpenLDAP 2.4.33, when compiled with
back-sql :
/etc/init.d/s
1 - 100 of 600 matches
Mail list logo
