Richard Hector wrote:
> Bob Proulx wrote:
> > In any case... I wanted to add an additional comment. I have
> > been thinking of doing something like this myself. I haven't done
> > it yet but if I were implementing this then I think I would have
> > ...
>
> This is, like many things you post, r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17/04/13 11:15, Bob Proulx wrote:
> In any case... I wanted to add an additional comment. I have
> been thinking of doing something like this myself. I haven't done
> it yet but if I were implementing this then I think I would have
> the server c
Le 22/04/2013 21:24, Bob Proulx a écrit :
Again let me apologize. Sorry for the diversion down the rabbit hole. Bob
No harm done : I was not in a hurry, and I learned very interesting things.
Thnaks for the help.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subjec
Erwan David wrote:
> Bob Proulx a écrit :
> >Am I completely misunderstanding the documentation on this? Maybe.
> >If so then I am sorry for misleading you along with me. I am
> >researching the problem. I think this is completely against the
> >documented interface.
>
> I added some traces in
Le 22/04/2013 01:19, Bob Proulx a écrit :
Erwan David wrote:
Ok, here is a policy-rc.d which does not work :
Since I led you down this road I set up a test system. I have been
using policy-rc.d in chroots seemlingly forever and they definitely
work there. They definitely prevent package upgra
Erwan David wrote:
> Ok, here is a policy-rc.d which does not work :
Since I led you down this road I set up a test system. I have been
using policy-rc.d in chroots seemlingly forever and they definitely
work there. They definitely prevent package upgrades from starting
daemons.
invoke-rc.d:
Erwan David wrote:
> I have problems withe the documentation of poilcy-rc.d, mainly te
> fact it seems to be for the sole usage of package maintainers, not
> of administrators of the machine, (see the fact taht alternatives
> MUST be used), and that I do not understand at all what an
> out-of-runle
Erwan David wrote:
> Bob Proulx a écrit :
> >Erwan David wrote:
> >>update-rc.d dovecot disable 2
> >>reboot, indeed dovecot is not started
> >>telinit 3
> >>dovecot does not start (even if there is a Sxxdovecot in /etc/rc3.d)
> >Hmm... It should start. I just tested this on a service locally and
Le 20/04/2013 23:37, Erwan David a écrit :
I have problems withe the documentation of poilcy-rc.d, mainly te fact
it seems to be for the sole usage of package maintainers, not of
administrators of the machine, (see the fact taht alternatives MUST be
used), and that I do not understand at all wh
Le 11/04/2013 08:25, Bob Proulx a écrit :
Erwan David wrote:
2) add at the beginning of each /etc/init.d/myserv a test to stop if
the encrypted partition is not mounted
Neither of those solutions seems acceptable for me.
So if someone has an idea, I'm listening.
I would do one of two things.
Le 17/04/2013 01:15, Bob Proulx a écrit :
Erwan David wrote:
update-rc.d dovecot disable 2
reboot, indeed dovecot is not started
telinit 3
dovecot does not start (even if there is a Sxxdovecot in /etc/rc3.d)
Hmm... It should start. I just tested this on a service locally and
it starts for me.
Erwan David wrote:
> update-rc.d dovecot disable 2
> reboot, indeed dovecot is not started
> telinit 3
> dovecot does not start (even if there is a Sxxdovecot in /etc/rc3.d)
Hmm... It should start. I just tested this on a service locally and
it starts for me. are you sure it isn't starting due
Le 13/04/2013 01:44, Rick Thomas a écrit :
On Apr 12, 2013, at 12:56 PM, Erwan David wrote:
However, booting in level 2 then using telinit 3 do not start the
services that I setup not to start in level 2... Thus I'll switch to
policy-rd method.
I'm surprised to hear that...
What did you
On Apr 12, 2013, at 12:56 PM, Erwan David wrote:
However, booting in level 2 then using telinit 3 do not start the
services that I setup not to start in level 2... Thus I'll switch to
policy-rd method.
I'm surprised to hear that...
What did you do to test? If you can give us some detai
Le 12/04/2013 17:00, Chris Bannister a écrit :
On Fri, Apr 12, 2013 at 09:53:17AM +0200, Erwan David wrote:
On Fri, Apr 12, 2013 at 06:12:55AM CEST, Rick Thomas said:
You mean booting in level 2, where dovecot, postgresql, etc. are
not started (but ssh is), then after giving the decryption key
On Fri, Apr 12, 2013 at 09:53:17AM +0200, Erwan David wrote:
> On Fri, Apr 12, 2013 at 06:12:55AM CEST, Rick Thomas
> said:
> > >You mean booting in level 2, where dovecot, postgresql, etc. are
> > >not started (but ssh is), then after giving the decryption key and
> > >mounting the encrypted par
On Fri, Apr 12, 2013 at 06:12:55AM CEST, Rick Thomas said:
> >You mean booting in level 2, where dovecot, postgresql, etc. are
> >not started (but ssh is), then after giving the decryption key and
> >mounting the encrypted partition switching to runlevel 3 where they
> >are started ?
> >
> >Indeed
On Apr 11, 2013, at 11:58 AM, Erwan David wrote:
Le 11/04/2013 20:53, Rick Thomas a écrit :
On Apr 11, 2013, at 12:22 AM, Erwan David wrote:
On Thu, Apr 11, 2013 at 08:25:56AM CEST, Bob Proulx
said:
Erwan David wrote:
2) add at the beginning of each /etc/init.d/myserv a test to
stop if
Le 11/04/2013 20:53, Rick Thomas a écrit :
On Apr 11, 2013, at 12:22 AM, Erwan David wrote:
On Thu, Apr 11, 2013 at 08:25:56AM CEST, Bob Proulx
said:
Erwan David wrote:
2) add at the beginning of each /etc/init.d/myserv a test to stop if
the encrypted partition is not mounted
Neither of th
On Apr 11, 2013, at 12:22 AM, Erwan David wrote:
On Thu, Apr 11, 2013 at 08:25:56AM CEST, Bob Proulx
said:
Erwan David wrote:
2) add at the beginning of each /etc/init.d/myserv a test to stop if
the encrypted partition is not mounted
Neither of those solutions seems acceptable for me.
So
On Thu, Apr 11, 2013 at 08:25:56AM CEST, Bob Proulx said:
> Erwan David wrote:
> > 2) add at the beginning of each /etc/init.d/myserv a test to stop if
> > the encrypted partition is not mounted
> >
> > Neither of those solutions seems acceptable for me.
> >
> > So if someone has an idea, I'm li
Erwan David wrote:
> 2) add at the beginning of each /etc/init.d/myserv a test to stop if
> the encrypted partition is not mounted
>
> Neither of those solutions seems acceptable for me.
>
> So if someone has an idea, I'm listening.
I would do one of two things. Either I would remove the /etc/r
Hi,
I need to setup a distant server where some services store their data
on an encrypted disk. I'd like to be able to reboot server, which
should then start a minimal set of services (including ssh), which
would allow me to then mount the encrypted disk through an ssh
connection, and start
23 matches
Mail list logo
