Network startup

At home I have my laptop with arch linux connected to my computer downstairs and the network is configured using dhcp. When I take my laptop with me to work it is not connected however and it sits there trying to connect to a computer that isn't there because it is not hooked up to anything. After a while it decides the network is down and gives me a login prompt.
Is there a way to reduce the time it waits before it gives me a prompt?
I have looked in the /etc/rc.d/network script but that doesn't make a whole lot of sense to me.
Anyone have any ideas on this? (perhaps reducing the time it waits is a bad idea...I dunno)
Thanks!
HC

... adding a "-t 12" to the ifup() /etc/rc.d/network was the first thing i changed after installing arch on my laptop and booting offline the first time waiting 1min ... it is a nice workaround (you have to use on some distros with simmilar startup-scripts) but it leads to some not nice things:
-> if you connect again to a LAN, you have to start the network manually (# /etc/rc.d/network start)
-> in shutdown-sequence, it will complain about network not running
=> it works, of course, but as i'm a semi-perfectionist, i was thinking about another way to solve the 1min-waiting:
i wanted to actually background "dhcpcd" imediately after start, so that the bootprocess can go on and the "dhcpcd" waits in the background for an answer the whole 60s
(at the UNI, we have a really slow dhcp-server, that if i had the -t to less than 28 i dont get an ip :-( but on the other side, i dont want to wait 29s to know that there is no LAN connected to my laptop)
unfortunately the dhcpcd has no option to go to background 
-> anybody to know how to say the dhcpcd to go to background (without rewriting the whole startup-scripts!)?
then i got an idea about another way to handle this: what about changing the /etc/rc.multi to offer to press a key (e.g. "n" == "This Daemon? [N]o thanx!") while a daemon is starting to stop the starting of this daemon
the advantage of a such solution: you dont need to set an timeout-value which may hinder you to connect to a LAN that responds slowly or have to wait for nothing
:::: the problem is: i have no idea how you can do this () --- gurus, please help ... the part that has to be changed looks now like this:
# Start daemons
for daemon in "${DAEMONS[@]}"; do
if [[ `echo $daemon | grep '^[^!]' | wc -l` -eq 1 ]]; then
/etc/rc.d/$daemon start
fi
done
-> shortly said: i want to be able to kill "/etc/rc.d/$daemon start" while it is running by pressing only one key on my keyboard

Similar Messages

  • My iMac tries to connect to old network startup

    Greetings,
    When I start up, I receive a message that my computer is trying to connect to the my old iMac, the one that I used with Migration Assistant to transfer files and such. That computer is no longer around, but the new one always searches for it.
    I have looked in Startup items, Airport preferences, recent servers in the Connect to Server part of the Finder, and found that there is an icon for "Network Startup" with a ? that I assume is the culprit. However, there is no obvious way to delete or cancel this.
    I checked the following discussion threads for answers:
    https://discussions.apple.com/message/13272616#13272616
    https://discussions.apple.com/message/5317530#5317530
    There were many useful suggestions, but so far no luck. There might be more out there, but I have been looking for a while now.
    Any help would be much appreciated.
    Thanks
    Ken

    Look in System Preferences > Accounts > Login Options > See if there is a Network Account Server defined.  If so, remove.
    Sounds like it's looking for a remote boot option.
    Regards,
    Captfred

  • Network Startup - how do i escape this

    Hi,
    My wife set my computer into "Network Startup" mode. You know using the Startup Disk control panel. Now my computer sits at startup waiting and displaying a globe.
    How do i get out of this mode?

    Hi threebean,
    First, when you post for assistance could you please indicate which Mac you have and which Mac OS you are running.
    Shut down your computer by holding down the Power Button for about 5 seconds, til you see a black screen. Now, grab your system restore disk. Now, press the Power Button, hold down the C key and insert the system disk all at the same time. Keep holding down the C key until you see the Apple logo.. An Installer window will open. Go to the top of the Menu and click Utilities/Startup Manager... don't freak, you are doing this from the system restore disk, not the internal disk, so when the Startup Manager window opens, it should populate your start up volumes. Click the one that says: MacintosHD 10.x.x (You won't see x's.. you'll see the Mac OS version. Now, click Restart... that will Restart your Mac from the internal drive.
    Carolyn

  • Wicd works, network startup scripts don't

    Title tells the story.  Using wicd-1.7 I can connect to wireless networks and the connection remains stable.  Using various combinations of rc.conf settings, netcfg, /etc/conf.d/wireless getting a connection is impossible at boot time and problematic after boot.  The problem occurs on every system I've tested arch on.  Wicd works, network startup scripts don't or only occasionally if some magic spell is properly cast.  I'm positive I've configured the settings in rc.conf correctly as I've been able to connect using those by some combination of rmmod WLAN_MODULE, modprobe WLAN_MODULE, /etc/rc.d/network restart or netcfg ESSID.  The requirement is that I am willing to go through the sequence multiple times. 
    I have just started testing arch and don't know if the network scripts worked before, but I assume they must have.  Were there changes in the network startup scripts recently?  I'm seeing many topics in the forums related to wireless problems.

    When I say that netcfg ESSID works after startup, I mean that it  works sometimes and that net-auto-wireless failed along with all other options that had the wireless start during boot.  I'm not sure which version I tried but this was a new install in December or January and I was ready to remove arch by the end of February.  A new version of wicd was released with some bug fixes that kept arch on the systems.  Had that failed this laptop would likely have a BSD on it.  Probably OpenBSD as I haven't tested that yet.
    My current settings are configured for wicd and not causing any significant issues, other than having to reload the wireless driver when resuming from suspend.

  • Startup Disk - only Network Startup available

    Hello,
    I've got a problem with startup. I have two partitions on my internal hard drive - HFS+ for Mac OS X Leopard and NTFS for Windows XP. I wanted to check the setting of startup disk but in the Startup Disk pane in System Preferences there is nothing but Network Startup. I can boot to Mac or Windows but I always have to wait like a minute while it tryes to connect or something. Do you know how to solve this issue?
    Thanks

    fatal_ wrote:
    Hello,
    I've got a problem with startup. I have two partitions on my internal hard drive - HFS+ for Mac OS X Leopard and NTFS for Windows XP. I wanted to check the setting of startup disk but in the Startup Disk pane in System Preferences there is nothing but Network Startup. I can boot to Mac or Windows but I always have to wait like a minute while it tryes to connect or something. Do you know how to solve this issue?
    Thanks
    For starters, deselect the network boot option so it does not spend time searching.
    Holding down the Option key as noted by another poster is one way to select your OS.
    Another option is to install rEFIt, a BSD boot selector program.
    http://refit.sourceforge.net/
    I am presuming you did not use BootCamp to install your Windows program, which might account for the missing boot manager that BC provides.

  • Network startup fails every time since 6/9 update [SOLVED]

    I use the netctl method to start the network on my various machines (with static IP addresses) and since doing full system upgrades on 6/9, which included an update to systemd, the network fails to start on bootup, every time. I have to start the network manually after logging in.
    I just read a post about a similar systemd-related problem (involving a new service) from which I quote: "yet another bunch of races to accompany the ones that have pestered the arch-linux bootup since that festering pile of race-ridden cs-student pipedream called systemd has been adopted into it."
    Race conditions in network startup have been troublesome for me since systemd appeared. It's been quite some time now and the problems keep appearing. Much as I like Arch, I may have to abandon it, because this kind of basic unreliability is not acceptable.
    Last edited by donallen (2014-06-10 18:34:35)

    Well, I did some more work on this, and I have a bit of egg on my face, with an excuse. You can decide for yourself whether you think it's a good one.
    I run multiple machines that I use for different circumstances, e.g., travel. I rsync my home directory when moving from one machine to another. They are all set up identically, with Arch. To avoid confusion about which machine has the latest changes in my home directory, the scripts I use for rsync-ing and my .bash_profile send emails to my gmail address, so I have an audit trail of what I have done. In the past, I *have* experienced systemd troubles (and know that because the network didn't come up reliably and there was discussion by others on this forum of problems similar to mine, with patches for the systemd scripts) and the first symptom I saw was the inability of my .bash_profile to send my 'I just logged in on system X' email. Since the system update yesterday, I have been seeing this symptom. My mistake was assuming, instead of verifying, that the network had not come up, and just starting the network manually with netctl (there was no error message from netctl that I was starting an already-started network profile). My confusion was abetted by the fact that there was a systemd update yesterday, according to pacman. But, in fact, when I realized I was making an unwarranted assumption and actually checked, I found that the network had come up and I now believe this is not a systemd issue.
    I think the issue is with mailx (mail), which also got updated yesterday. The mail I send requires authentication by the smtp server I'm using, and my scripts provide that, using the smtp-auth-* options to mail. This worked until yesterday. Looking at the mail man page, it appears that mail configuration and these options are about to change with version 15. The current version is 14.7 and purports to support both the old and new-style configuration and options. To turn on the new style, you supposedly invoke an option, -v15-compat, which is off by default. The options I'm using are not v15 compatible, but should work, since I have not provided the option to turn on v15 support. But it appears they do not.
    I will mark this thread SOLVED, since my original diagnosis was wrong.

  • Remove the network startup

    I juz found out there is a "network startup" on my system preference/startup disk, there was only one hard drive before, and i dunno why there is one there now....how can i remove it, or why is it there?

    It's there for everyone, and is completely normal. It allows you to boot from a system on the network, rather than from the internal hard drive.

  • Starting up in Network startup

    Can anyone explain to me exactly how network startup works and how to do it. when I clicked on it and clicked restart it didn't do anything. So I highlighted network startup and clicked the lock to prevention of further changes and restarted from the apple menu thinking it would start in network mode since the option was locked in but still nothing. can anyone help?
    24'' iMac - 15'' MacBook Pro   Mac OS X (10.4.8)   (iPhone in JUNE!!!)

    When the computer's startup disk is set to start up from a disk on the network, it will attempt to connect to a Mac OS X Server or other system which has an available NetBoot image. If you change the startup disk and then close the padlock immediately, System Preferences may not be able to properly write the setting; you need to go to another pane, or the main screen, or quit System Preferences to save the changes first if you will be closing the padlock.
    (20419)

  • My hard drive is no longer shows up in Sys Pref's. It only shows a network startup. Why and what can I do?

    Greetings,
    When I go to System Preferences, Startup Disk I see an icon that says "Network Setup" with an icon that has a question mark on it.
    I am hard wired to a router but think that I should still have the start up disk icon there.
    Does anybody have any idea's or knowledge on this subject?
    Thank you.
    macuser222

    Greetings baltwo,
    I just switched over to my administrator account and the hard drive is in Sys. Pref, start up disk. on that account! The problem is only on my standard account!
    Would it be best for me to remove the secondary account and create a new one?
    Actually, I really only have the secondary account as I was taught years ago to use a standard account as opposed to an administrator account for security purposes.  Is that still recommended?
    Also, thank you for bringing the 10.6.5 and 10.6.7 to my attention.
    Regards,
    macuser222

  • Can't start ... tried a bunch of things ... what about network startup??

    Greetings and salutations all you helpful folks,
    I am battling away trying to get my ibook G4 to start.
    I have mounted it as a terminal and it works fine as that, and I have retrieved all the data that I need from the hard drive but now I would like to fix it and use it again.
    So, I have tried running disk utility but it says that there is nothing wrong and the volume checks.
    I have tried putting G4 OSX install disk in but it won't boot from the CD with the "C" held down.
    I then have to use open firmware to eject the CD to try the next thing, whatever that might be ...
    but when the computer is in terminal mode I can get it to read the cd in the drive just fine, but when it boots on it's own it just doesn't seem to want to do it. It does spin the disk and seem to read it but then I get a message that says that I need to restart my computer and so I do and nothing better happens.
    So, on a whim I tried my G5 disks from my iSight. I don't know why, I'm just desperate. And it told me it couldn't install that software and would I like to restart from the network or the harddrive.
    and this started some questions in my head.
    This G4 is on a network with a G5. What does "network start up" mean? Can I convince this little laptop to use the G5 as it's startup disk? Would that work? Could that work?
    Next question, I seem to have to problems starting up into Open Firmware/ Is there something I can do in that mode that might check out my drive and or repair it and/or get it to boot from the CD?
    I really need this little laptop on my system. It is used by other folks for simple things like internet and mail and ordering and now that it is down they are fighting for my machine ... aargh!!
    help? any help is reallly needed now. HOw can these drives be dead or non functioning when I can read them and spin them from another computer? I feel like this is just a software problem and I should be able to get by it ... but it has me stumped. not hard considering how much of a computer non-techno geek that I am. Just a user am I. And a frustrated one at that!!
    smiles
    kt

    wait wait I made a typo
    I said it seems to have problems starting in open firmware ... but what I meant was
    I seem to have NO problems starting up in open firmware ...
    sorry
    kt

  • Dhcpcd not starting correctly via rc.d/network startup script

    Whenever I try to setup my network with /etc/rc.d/network  I always fail to get a lease.  When I execute the same command manually, I get an IP and everything associated with it.
    I've added the lines below to the network script for debugging:
    echo 'whoami: '`whoami`
    echo 'which dhcpcd: '`which dhcpcd`
    echo '$DHCPCD_ARGS: '$DHCPCD_ARGS
    echo '$interface: '$interface
    I've set it to debug mode, and have the output when running it below
    [foo@bar etc]$ sudo rc.d/network start
    :: Starting network [BUSY]
    whoami: root
    which dhcpcd: /usr/sbin/dhcpcd
    $DHCPCD_ARGS: -d
    $interface: eth0
    dhcpcd[3483]: version 5.5.6 starting
    dhcpcd[3483]: eth0: using hwaddr 52:44:a3:6c:c2:72
    dhcpcd[3483]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason PREINIT
    dhcpcd[3483]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason NOCARRIER
    dhcpcd[3483]: eth0: carrier acquired
    dhcpcd[3483]: eth0: using hwaddr 52:44:a3:6c:c2:72
    dhcpcd[3483]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
    dhcpcd[3483]: eth0: carrier lost
    dhcpcd[3483]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason NOCARRIER
    dhcpcd[3483]: eth0: waiting for carrier
    dhcpcd[3483]: eth0: carrier acquired
    dhcpcd[3483]: eth0: using hwaddr 52:44:a3:6c:c2:72
    dhcpcd[3483]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
    dhcpcd[3483]: eth0: broadcasting for a lease
    dhcpcd[3483]: eth0: sending DISCOVER (xid 0xc83b6419), next in 4.84 seconds
    dhcpcd[3483]: eth0: sending DISCOVER (xid 0xc83b6419), next in 8.24 seconds
    dhcpcd[3483]: eth0: sending DISCOVER (xid 0xc83b6419), next in 16.37 seconds
    dhcpcd[3483]: timed out
    Yet I run the same command manually and everything's happy:
    [spitfire@killdesk etc]$ sudo /usr/sbin/dhcpcd -d eth0
    dhcpcd[3511]: version 5.5.6 starting
    dhcpcd[3511]: eth0: using hwaddr 52:44:a3:6c:c2:72
    dhcpcd[3511]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason PREINIT
    dhcpcd[3511]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
    dhcpcd[3511]: eth0: broadcasting for a lease
    dhcpcd[3511]: eth0: sending DISCOVER (xid 0xfddd3649), next in 4.66 seconds
    dhcpcd[3511]: eth0: offered 192.168.1.1 from 192.168.1.254
    dhcpcd[3511]: eth0: sending REQUEST (xid 0xfddd3649), next in 3.31 seconds
    dhcpcd[3511]: eth0: acknowledged 192.168.1.1 from 192.168.1.254
    dhcpcd[3511]: eth0: checking for 192.168.1.254
    dhcpcd[3511]: eth0: sending ARP probe (1 of 3), next in 1.94 seconds
    dhcpcd[3511]: eth0: sending ARP probe (2 of 3), next in 1.40 seconds
    dhcpcd[3511]: eth0: sending ARP probe (3 of 3), next in 2.00 seconds
    dhcpcd[3511]: eth0: leased 192.168.1.1 for infinity
    dhcpcd[3511]: eth0: adding IP address 192.168.1.1/24
    dhcpcd[3511]: eth0: adding route to 192.168.216.0/24
    dhcpcd[3511]: eth0: adding default route via 192.168.1.254
    dhcpcd[3511]: eth0: writing lease `/var/lib/dhcpcd/dhcpcd-eth0.lease'
    dhcpcd[3511]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason BOUND
    dhcpcd[3511]: forking to background
    dhcpcd[3511]: forked to background, child pid 3537
    What am I doing wrong, and/or what can I do to fix this?

    Maybe I got something wrong here but didn't sspitfire write that dhcpcd only works when starting it manually after it failed at startup? What exactly is "noip4all" supposed to do, I'm asking because it didn't work for me.  I tried "noip4ll" like written in dhcpcds manpage without any effort .  "noarp" and "waitip" also had no positive effect. Maybe I leave dhcpcd in the rc.local even if it's a bit of a dirty solution. ("noarp" and "waitip" I gathered from the dhcpcd  manpage).

  • Help Network Startup delay

    Hi,
    About a year ago we upgraded most of our computers from 10.3.9 to 10.4.x. Ever since then there is a 30 to 40 sec delay at startup before the Network initializes. This issue is only present in 10.4.x and it happened the 1st day we upgraded to 10.4.x. It does not happen on either of the two remaining 10.3.9 machines.
    Basically, on the 10.3.9 machines the Network is available (I can surf the net and mount Network volumes) as soon as the Desktop finishes loading. On the 10.4.x machines, there is a 30 to 40 second delay between the time the Desktop finishes loading and when the Network is really available to surf or Mount Network Volumes.
    I have opened the Network Preference and before our Network is really active (so I can Surf the Net) I have a valid IP Address and the Green Light is lit, indicating that the Compter thinks it has a valid connection, even though it doesn't. This has happened on every version of 10.4.x we have used, all the way up to and including 10.4.9.
    We were using a 4 year old Router up to about 3 weeks ago, so I was hoping that upgrading the Router might help this situation, but it didn't. Even our Network with the new Router has the same problem.
    Has anyone run into this before? Any suggestions?
    Thanks
    Kalagan

    I am in the process of updating the Firmware on our Cisco Gigabit Switches to see if that will help.
    Just an update
    Kalagan

  • Network Startup Mistake

    I accidentally set my startup disk as "Network". Now, when I boot I get a blinking globe, then a blinking question mark on a folder. I have tried booting from the install disk and nothing happens. How can I change the startup back to the OS X folder?

    Thanks John,
    That worked, I am able to see the icon for the hard drive or the CD disk, however my mouse won't function so I can't choose to boot from the CD. I can hit enter and the system chooses the hard drive, but it hangs.
    Any other advice?
    Thanks so much. Lisa

  • Imac will not see my hard drive on start up, wants to start from network start up disk that does not exist. How to get rid of it? So there is just one choice / my hard drive.

    I have a Intel duo Imac. Everything has been running relatively smoothly for a few years now. All of a sudden my computer will not start. I get the flashing folder with a question mark.
    When I go to Start up disk in my system perfernces while the computer is on. I see 2 possible choices. One is my hard drive with the operating system shown. The other is a non-existant Network Start up disk with a question mark in it ( looks like a hard drive with a question mark and it say's its a "network start up disk).
    All I think I want to do is get rid of the Network startup with the question mark. I can not find anywhere how one can just remove an old or non existant start up disk without reformatting.
    I believe this came from a clients hard drive who had a network system on it. We no longer have that drive. It no longer exists. But a latent icon shows up in start up disk.
    When I go to change the start up disk. I can change it to either the hard drive or the network with the question mark. But when I select my hard drive and then got to restart the computer. I get the flashing folder with a question mark on start up. I have also seen the flashing globe a couple times.
    When I attempt to run disk utility from may install disk ( holding down "C" on start-up ). Disk utility does not see my hard drive. Just the Apple install disk with the disk utility on it.
    What can I do to remedy this short of re-installing? Will a program like Disk Warrior or Tech Tool help?

    Thank you. That's what I thought will need to happen.
    One more question. I tried using the Apple install disk that came with the computer. It's an OS 10.5.6 disk. It does not see my 10.6.8 system internal hard drive to repair. All it see's is itself 10.5.6 disk. Do you think I can use a 10.8+ disk utillity since that is a higher system it will see the 10.6.8. Where the 10.5.6 does not?
    I don't want to turn the computer off for fear I'll get the question mark again. P-Ram got me going last time but for how long I don't know?  It would be nice to be able to turn the computer off for the night and startup as usual to give it a rest and try to reset itself.
    Thanks for your help, I know I will eventually need to re-install. But I am in the middle of a project with tight deadlines and all I can do right now is back-up. Trying to migrate to another computer temporarily to finish the job. That's a lot of extra work in the short time also.
    Just trying to put a band-aid on it for another couple weeks.

  • Blue screen and "startup disc is full" error

    My iPad2 is frozen with an "unaable to download app.....' error and after unsuccessfully trying to turn it off, I attached it to my MacBook Pro to try to sync it.  Nothing happened so i restarted my Macbook Pro.  Upon start up, the MP screen went blue and the error message "Your Startup disk is full" appeared. I hit OK & was left with a blue screen. 
    After disconnecting the ipad2 from the MP and restarting the Mp, same issue appeared.  Turned MP off and started in single user mode (Cmd-S).  Typed 'reboot'. came back up again with blue screen. 
    Tried single user mode again & typed 'fsck -fy'. System ran a checking routine and came back with "**The volume MacIntosh HD appears to be OK".  Entered 'shutdown -r now' to same results - blue screen , start up full -
    Now what?
    Looks like I'm running Mac OS X, 10.6.8
    when I go to start up ion via the option key network startup has a ? Mark.  Chose the startup with Mac OS...
    Same blue screen & error message
    I can get to system preferences using the option key but that's it

    I understand CS4 does like to use a lot of space for scratch space when making complicated image changes. Verify you are able to control how much scratch space it uses in such functions. If you aren't, maybe it is indicative of needing a separate partition or hard drive to store CS4 temporary drive. When you have a separate partition or hard drive, you can erase the drive, and avoid fragmentation of files larger than 20 MB. Normally Mac OS X doesn't suffer fragmentation, except with large files as explained here*:
    http://www.macmaps.com/directoryfaq.html#DEFRAG
    - * Links to my pages may give me compensation.

Maybe you are looking for