[SOLVED] Unable to run rc.inet1 after logging in

ash_zz_00 · 12-11-2009, 10:43 PM

Hi,

Slackware 12.2 on HP dv6t Notebook.

Sometimes I log in without connecting to the network. Now to connect to the network after the fact, I tried to run rc.inet1 but I get an error. However, it does run successfully during startup. The script does have execute permissions. What am I missing?

Code:

bash-3.1# ls -l rc.inet1
-rwxr-xr-x 1 root root 9437 2008-12-07 23:53 rc.inet1

bash-3.1# rc.inet1
bash: rc.inet1: command not found

Thanks in advance,

Ash.

vinaytp · 12-12-2009, 01:08 AM

Hi,

Try with,

Code:

bash-3.1# ./rc.inet1

Cheers !!

affinity · 12-12-2009, 01:39 AM

Are you acting as root? Also you would need to do the full path and a switch, in Slackware 13 the full path is "/etc/rc.d/rc.inet1". You can use the following switches "start; stop; restart". So in your case the process would be the following:

Code:

su
/etc/rc.d/rc.inet1 start
ping google.com

Pinging is just a quick test to see if you are online or not after starting the service.

ash_zz_00 · 12-12-2009, 09:25 PM

Thank you for the suggestions. It worked.

Just wondering, so is it typical in Linux to not use the present working directory? Is it always recommended to use the full path or at least explicitly specify the directory?

Regards,

Ash.

affinity · 12-13-2009, 08:08 PM

Quote:

Originally Posted by ash_zz_00

Thank you for the suggestions. It worked.

Just wondering, so is it typical in Linux to not use the present working directory? Is it always recommended to use the full path or at least explicitly specify the directory?

Regards,

Ash.

You don't have to include the full path if you are in the file's current directory, I just did it in the example for future reference and because that way you could just open the shell and run the command without changing directories.

chrism01 · 12-13-2009, 10:32 PM

Quote:

is it typical in Linux to not use the present working directory?

Yes, it's a security issue, especially for root. If someone manages to get their own prog into your home dir (where you normally login), then they can substitute a trojan for eg the 'ls' cmd and own you. This goes double for root obviously.

Normally, you'd give either an absolute path (eg /etc/rc.d/rc.inet1) if you are some completely unrelated dir (or it's a cron entry) or you can use a 'relative' path eg ./rc.inet1 if you are in the /etc/rc.d/ dir.

http://rute.2038bug.com/index.html.gz
http://tldp.org/LDP/Bash-Beginners-G...tml/index.html

ash_zz_00 · 12-22-2009, 01:38 PM

Thanks, that makes sense.