Hi there
Rob van der Putten wrote:
More weirdness:
I can start inputattach as root, but not as a normal user using a suid
script.
The thing to do is to write a start script and start the mouse just
_after_ XDM. This works both with and without .legacy-bootordering.
I'll put more info on my
Hi there
Andrei POPESCU wrote:
Yes it is. Why do you expect this to be a problem?
More weirdness:
I can start inputattach as root, but not as a normal user using a suid
script.
Regards,
Rob
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscrib
Hi there
Rob van der Putten wrote:
asterisk is not in /etc/init.d/.depend.*
'insserv /etc/init.d/asterisk' fixed this
One would expect this to run on install.
Regards,
Rob
--
Alphabet soup sux. Specify your charset;
http://en.wikipedia.org/wiki/Mojibake#Example
--
To UNSUBSCRIBE, email t
On Tue, Dec 4, 2012 at 9:02 AM, Rob van der Putten wrote:
> Tom H wrote:
>>
>> AFAIUI, "$remote_fs" being "Required-Start" for bind9 means that nfs
>> volumes have to be mounted for bind9 to be started not that
>> nfs-kernel-server's shares have to be exported.
>
> This box does both.
It dosn't m
Hi there
Tom H wrote:
AFAIUI, "$remote_fs" being "Required-Start" for bind9 means that nfs
volumes have to be mounted for bind9 to be started not that
nfs-kernel-server's shares have to be exported.
This box does both.
Regards,
Rob
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.de
Hi there
Rob van der Putten wrote:
Tom H wrote:
Do the logs say why?
Nothing.
If not, check how the scripts are numbered with
and without legacy ordering to figure out what asterisk's
"Required-Start" and "Should-Start" might be missing.
I'll try.
asterisk is not in /etc/init.d/.depe
On Mon, Dec 3, 2012 at 10:47 AM, Rob van der Putten wrote:
> Rob van der Putten wrote:
>> Tom H wrote:
>>>
>>> Why a circular dependency? You're adding it to nfs-kernel-server not
>>> to bind9.
>>
>> '$remote_fs' confused me. '/etc/insserv.conf' cleared things up.
>
> Actually I'm still confused.
On Lu, 03 dec 12, 16:39:33, Rob van der Putten wrote:
> Andrei POPESCU wrote:
>
> >~/.xsessionrc
>
> If I understand correctly this stuff is sourced, not run.
Yes it is. Why do you expect this to be a problem?
Kind regards,
Andrei
--
Offtopic discussions among Debian users and developers:
http
On 2012-12-03 16:47 +0100, Rob van der Putten wrote:
> Rob van der Putten wrote:
>
>> Tom H wrote:
>
>>> Why a circular dependency? You're adding it to nfs-kernel-server not
>>> to bind9.
>>
>> '$remote_fs' confused me. '/etc/insserv.conf' cleared things up.
>
> Actually I'm still confused.
>
> Fr
Hi there
Tom H wrote:
Do the logs say why?
Nothing.
If not, check how the scripts are numbered with
and without legacy ordering to figure out what asterisk's
"Required-Start" and "Should-Start" might be missing.
I'll try.
Regards,
Rob
--
To UNSUBSCRIBE, email to debian-user-requ...@l
Hi there
Rob van der Putten wrote:
Tom H wrote:
Why a circular dependency? You're adding it to nfs-kernel-server not
to bind9.
'$remote_fs' confused me. '/etc/insserv.conf' cleared things up.
Actually I'm still confused.
From /etc/insserv.conf;
#
# All remote filesystems are mounted (n
Hi there
Andrei POPESCU wrote:
~/.xsessionrc
If I understand correctly this stuff is sourced, not run.
Regards,
Rob
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debia
On Du, 02 dec 12, 16:26:46, Rob van der Putten wrote:
>
> This still leaves me with my X + mouse problem.
> Is there a (standard) way to run a script when starting X?
~/.xsessionrc
Kind regards,
Andrei
--
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mai
Hi there
Tom H wrote:
Why a circular dependency? You're adding it to nfs-kernel-server not to bind9.
'$remote_fs' confused me. '/etc/insserv.conf' cleared things up.
"Provides: bind9" means that the bind9 init script provides the bind9
boot facility.
"bind9" is one of the facilities that
On Sun, Dec 2, 2012 at 10:49 AM, Rob van der Putten wrote:
> Rob van der Putten wrote:
>
> I just found out:
> Without .legacy-bootordering asterisk won't start.
Do the logs say why? If not, check how the scripts are numbered with
and without legacy ordering to figure out what asterisk's
"Require
On Sun, Dec 2, 2012 at 10:26 AM, Rob van der Putten wrote:
> Tom H wrote:
>> You can use an insserv override to add
>> Should-Start: $named
>> Should-Stop: $named
>> to the nfs-kernel-server LSB headers to ensure that bind starts before
>> nfs.
>
> The bind9 script says: Provides: bind9
Hi there
Rob van der Putten wrote:
The bind9 script says: Provides: bind9
I assume this is somehow translated into: Provides: named.
Where can I find more on this subject.
How do I check that adding 'Should-Start: $named' and 'Should-Stop:
$named' won't introduce a circular dependency?
Anywa
Hi there
Tom H wrote:
You can use an insserv override to add
Should-Start: $named
Should-Stop: $named
to the nfs-kernel-server LSB headers to ensure that bind starts before nfs.
The bind9 script says: Provides: bind9
I assume this is somehow translated into: Provides: named
On Thu, Nov 29, 2012 at 5:02 PM, Rob van der Putten wrote:
>
> When Upgrading from Lenny to Squeeze I run into trouble because NFS wanted
> to mount before Bind was running. legacy-bootordering fixed this for me.
You can use an insserv override to add
Should-Start: $named
Should-Stop: $named
to t
Hi
Does wheezy support /etc/init.d/.legacy-bootordering?
When Upgrading from Lenny to Squeeze I run into trouble because NFS
wanted to mount before Bind was running. legacy-bootordering fixed this
for me.
I also use legacy-bootordering on my GUI box: I use /etc/rc.local to
start inputattach
20 matches
Mail list logo
