Execution of /etc/rc.d/rc.local - users - Fedora Mailing-Lists

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

1995

1994

1993

1992

1991

1990

1989

1988

1987

1986

1985

1984

1983

1982

1981

1980

Execution of /etc/rc.d/rc.local

/dev/ttyUSB0 changes to...

Evolution indiexing error

Geoffrey Leach

Tuesday, 15 May 2012 Tue, 15 May '12

4:13 p.m.

Recently (who can track all those new kernels?) I've noticed that the commands in rc.local are not running, from which I conclude that it's not being executed. systemctl says: "rc-local.service (loaded active running)" Any ideas.

Reply

Show replies by date

Bruno Martins

Tuesday, 15 May Tue, 15 May

5:23 p.m.

On 05/15/2012 10:13 PM, Geoffrey Leach wrote:

Recently (who can track all those new kernels?) I've noticed that the commands in rc.local are not running, from which I conclude that it's not being executed. systemctl says: "rc-local.service (loaded active running)" Any ideas.

If you can, please show us your /etc/rc.d/rc.local contents and file permissions. But that's weird, because I think usually it would give an error on starting up.

Reply

Geoffrey Leach

6:52 p.m.

On 05/15/2012 03:23:03 PM, Bruno Martins wrote:

On 05/15/2012 10:13 PM, Geoffrey Leach wrote: > Recently (who can track all those new kernels?) I've noticed that > the commands in rc.local are not running, from which I conclude > that it's not being executed. systemctl says: "rc-local.service > (loaded active running)" > > Any ideas. If you can, please show us your /etc/rc.d/rc.local contents and file permissions. But that's weird, because I think usually it would give an error on starting up.

root@puget[10]->cat /etc/rc.d/rc.local #! /bin/sh # Run by /lib/systemd/system/rc-local.service /usr/local/bin/check_running & systemctl restart nfs-lock.service systemctl restart nfs-idmap.service systemctl restart nfs-server.service /usr/bin/synclient TouchpadOff=1 exit 0 root@puget[11]->ls -l /etc/rc.d/rc.local -rwxr-xr-x 1 root root 239 May 14 21:16 /etc/rc.d/rc.local*

Reply

Kevin Fenzi

Wednesday, 16 May Wed, 16 May

11:14 a.m.

On Tue, 15 May 2012 16:52:08 -0700 Geoffrey Leach <geoff(a)hughes.net> wrote:

root@puget[10]->cat /etc/rc.d/rc.local #! /bin/sh

^ you have a " " here that shouldn't be there. Should be simply: "#!/bin/sh" kevin

Reply

Ed Greshko

11:19 a.m.

On 05/17/2012 12:14 AM, Kevin Fenzi wrote:

On Tue, 15 May 2012 16:52:08 -0700 Geoffrey Leach <geoff(a)hughes.net> wrote: > root@puget[10]->cat /etc/rc.d/rc.local > #! /bin/sh ^ you have a " " here that shouldn't be there. Should be simply: "#!/bin/sh"

That was my theory too.... But I like to test my theories.... So I created an rc.local file with the following contents... #! /bin/sh -e #exit 0 touch /tmp/XXXX and it worked just fine.... -- Never be afraid to laugh at yourself, after all, you could be missing out on the joke of the century. -- Dame Edna Everage

Reply

Geoffrey Leach

11:48 a.m.

On 05/16/2012 09:14:11 AM, Kevin Fenzi wrote:

On Tue, 15 May 2012 16:52:08 -0700 Geoffrey Leach <geoff(a)hughes.net> wrote: > root@puget[10]->cat /etc/rc.d/rc.local > #! /bin/sh ^ you have a " " here that shouldn't be there. Should be simply: "#!/bin/sh"

Blush! The # is where it should be. Just a copy error.

Reply

Heinz Diehl

2:23 p.m.

On 16.05.2012, Kevin Fenzi wrote:

^ you have a " " here that shouldn't be there. Should be simply: "#!/bin/sh"

This is not true, you can hav as many blanks as you like. Try it.

Reply

Tom Horsley

2:50 p.m.

On Wed, 16 May 2012 21:23:39 +0200 Heinz Diehl wrote:

This is not true, you can hav as many blanks as you like. Try it.

Not as many as you like - I think the exec() service looks only at about the first 32 characters or something like that.

Reply

Kevin Fenzi

5:15 p.m.

On Wed, 16 May 2012 15:50:14 -0400 Tom Horsley <horsley1953(a)gmail.com> wrote:

On Wed, 16 May 2012 21:23:39 +0200 Heinz Diehl wrote: > This is not true, you can hav as many blanks as you like. > Try it. Not as many as you like - I think the exec() service looks only at about the first 32 characters or something like that.

I stand corrected. ;) So, why are you restarting nfs services there? The synclient won't work as rc.local has no connection to your DISPLAY to make changes. How else are you seeing that commands there aren't running? kevin

Reply

Geoffrey Leach

5:43 p.m.

On 05/16/2012 03:15:24 PM, Kevin Fenzi wrote:

On Wed, 16 May 2012 15:50:14 -0400 Tom Horsley <horsley1953(a)gmail.com> wrote: > On Wed, 16 May 2012 21:23:39 +0200 > Heinz Diehl wrote: > > > This is not true, you can hav as many blanks as you like. > > Try it. > > Not as many as you like - I think the exec() service looks > only at about the first 32 characters or something like that. I stand corrected. ;) So, why are you restarting nfs services there? The synclient won't work as rc.local has no connection to your DISPLAY to make changes. How else are you seeing that commands there aren't running?

Thanks for the tip on synclient Restarting nfs services is being done because that was necessary in order to get a connection from the client. Admittedly that was several kernels ago :-)

Reply

Kevin Fenzi

Thursday, 17 May Thu, 17 May

11:47 a.m.

On Wed, 16 May 2012 15:43:46 -0700 Geoffrey Leach <geoff(a)hughes.net> wrote:

Thanks for the tip on synclient Restarting nfs services is being done because that was necessary in order to get a connection from the client. Admittedly that was several kernels ago :-)

Yeah, that seems odd. I'd just let systemd start them and then if something is not working, track that down and fix it. kevin

Reply

4422

days inactive

4424

days old

users@lists.fedoraproject.org

Manage subscription

10 comments

6 participants

tags (0)

participants (6)

Bruno Martins
Ed Greshko
Geoffrey Leach
Heinz Diehl
Kevin Fenzi
Tom Horsley