Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
is just ps finding the command you are currently running (ps aux | grep iptables). I assume grep is aliased to grep --color on you system)
I'm struggling a bit with the error you are getting. What distro are you running, and do you compile your own kernel? I'll have a look in more detail later if I get a system booted that mount this way.
A workaround (kin of takes us back to step 1) would be to add "mount -a" to rc.local
i'm running pclinuxos 2007. i'm not advanced enough to compile my own kernel. i'm running the kernel supplied with the release.
the error just simply looks like eth0 isnt fully up and running yet, which is why cifs is erroring on connecting to ipv4. I think if i put mount -a in my rc.local, i will run into the same problem... rc.local runs just a bit too soon before eth0 is fully up, which is why when i originally tried putting my mounts in rc.local, they did not connect.
i'd have no problem using a workaround, just as long as everything worked.
the fact that eth0 isn't up is exactly what the _netdev option is meant to deal with. I don't quite see why the invalid option error (you only have one "_" there? no space before it?
Dodgy workaround
in root's crontab, using crontab -e add at the very top
I dont think i was editing the right crontab with crontab -e... the bottom of the file says "/tmp/crontab.XXXXna6Awc" 1L, 66C
I did nano /etc/crontab, and that file does contain some text. should I put @reboot mount -a at the very top before SHELL=/bin/bash, or put it just after?
No - that's the "system" crontab (although it may work in there)
You should have each user's crontab file in (somewhere like) /var/spool/cron (chack with "find / -type d -name cron". If you go "cat /var/spool/cron/root", you should see the same file you see when you enter crontab -e.
I think you'll find the editing of a temp file is normal - it only gets over-written when you exit the editor.
"cat /var/spool/cron/root" brings up no such file or directory
you'll have to excuse me, i have no idea how to use vim. i've always used pico and nano. man vim does not help me at all.
so i do crontab -e, which brings me to a tmp file since one does not exist. i tried to enter @reboot mount -a, and tried :save. but whenever i do that and :quit, i go back into the file with crontab -e and the file is not saved, it is again blank. i have no clue how to save the file in vim, and the man page gives no explanation of usage once inside the editor.
Okay, the changes are saved. before i reboot, i want to make sure i edited the file properly. I didnt know how to start editing the file, when i started typing nothing happened until I got to the "b" in "reboot"... im assuming you have to hit "e" to start editing the file. so heres my crontab file:
# min(0-59) hours(0-23) day(1-31) month(1-12) dow(0-7) command
@reboot mount -a
note it still says tmp at the bottom... but when i did :wq <enter> it did tell me it made new crontab for root. so i guess everything is okay. I'll wait till you post back before i reboot in case i did something wrong.
Rebooted after the crontab edit, and that didnt work. also put mount -a into rc.local, which didnt work either. i'm going to remove the entry's in crontab and rc.local since they dont work.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.