OVI starts on boot up

How can I stop OVI starting on boot?
I have unchecked it the program but it is ignoring it.
Cheers
E71

You can go into options of Nokia Ovi Suite -Start Up and uncheck the option Start Nokia Ovi Suite automatically when your computer starts up
Helpful information, then dont forget to hit the kudos star :-) Or say it accepted solution and thanks

Similar Messages

Trying to create a service that starts at boot

People,
I'm trying to create a service that will start at boot (in single-user mode, actually). I am up and running but I do NOT want to run the service now. I only want to run the service when the machine reboots.
I've been rummaging around all day trying to figure this out but I'm stuck. I can create a service that runs. I can create an XML file in /var/svc/manifest/site/patch-install.xml that will be read when I boot- because after I boot, I can list the service:
svcs -a | grep patch
disabled       18:23:23 svc:/site/patch-install:defaultI have inserted the following in my xml:
<create_default_instance enabled='true' />and also
<create_default_instance enabled='false' />but it makes no difference. Anyone have any idea? What is the purpose of create_default_instance? I don't understand; item 9 on http://www.sun.com/bigadmin/content/selfheal/sdev_intro.html seems rather opaque to me.
Also, what exactly is the purpose of /var/svc/profile/ ? I tried putting some code to enable my xml but it didn't do anything. Just wondering if this might fit into the picture.
BTW, I do not want the login prompt to appear until my method is complete.
Thanks.
-mschwage
Here fyi is my /var/svc/manifest/site/patch-install.xml file:
<?xml version="1.0"?>
<!DOCTYPE service_bundle SYSTEM "/usr/share/lib/xml/dtd/service_bundle.dtd.1">
<service_bundle type='manifest' name='Patches:patch-install'>
<service
        name='site/patch-install'
        type='service'
        version='1'>
        <create_default_instance enabled='false' />
        <single_instance />
        <dependent
                name='patch-install_single-user'
                grouping='require_all'
                restart_on='none'>
                <service_fmri value='svc:/milestone/single-user' />
        </dependent>
        <exec_method
                type='method'
                name='start'
                exec='/var/tmp/S92delay'
                timeout_seconds='86400' />
        <exec_method
                type='method'
                name='stop'
                exec=':true'
                timeout_seconds='0' />
        <property_group name='startd' type='framework'>
                <propval name='duration' type='astring' value='transient' />
        </property_group>
        <stability value='External' />
        <template>
                <common_name>
                        <loctext xml:lang='C'>
                        Install patchset upon boot.
                        </loctext>
                </common_name>
        </template>
</service>
</service_bundle>

Hushpuppy wrote:
People,
I'm trying to create a service that will start at boot (in single-user mode, actually). I am up and running but I do NOT want to run the service now. I only want to run the service when the machine reboots.I'd probably create the service now (by importing the manifest manually rather than waiting for the reboot), then set general/enabled in the default instance to be be true with svcprop. That should tell it to start at boot, but not enable it immediately.
I've been rummaging around all day trying to figure this out but I'm stuck. I can create a service that runs. I can create an XML file in /var/svc/manifest/site/patch-install.xml that will be read when I boot- because after I boot, I can list the service:Yes, that's the default. Or you can load it immediately to create the service now.
# svccfg import patch-install.xml
I have inserted the following in my xml:
<create_default_instance enabled='true' />and also
<create_default_instance enabled='false' />but it makes no difference. Anyone have any idea? What is the purpose of create_default_instance? I don't understand; item 9 on http://www.sun.com/bigadmin/content/selfheal/sdev_intro.html seems rather opaque to me.There's a difference between a "service" like network/smtp or console-login and an "instance" like network/smtp:sendmail or console-login:default. In most cases, you just want a single "default" instance of your service. The above line sets the default instance 'enabled' property to true or false. When I import your manifest as is, the service comes in as 'disabled'. If I set it to true, it comes in as 'maintenance' (almost certainly because it was enabled, tried to start, and couldn't find the start method on my machine).
Also, what exactly is the purpose of /var/svc/profile/ ? I tried putting some code to enable my xml but it didn't do anything. Just wondering if this might fit into the picture.'profiles' are loaded exactly once, and they are mainly used to set certain services to enabled or disabled.
3 of them are loaded if present, platform.xml, generic.xml, and site.xml. The last is not generated by the OS, but left for you to use. But it's usually only useful as a "first boot" type thing. Because if you make changes to it, it will not be reread. This isn't usually a problem because after first boot you're in control of the services. The usual thing is that at first boot the manifests load to create services, then the profiles are loaded to set then enabled or disabled. This isn't possible before that point because there's no service to modify yet.
BTW, I do not want the login prompt to appear until my method is complete.Any login prompt like a network login, or only the console login prompt? If the latter, then you'll want a dependency so that system-console-login depends on your service. But if your service has a problem at boot time, you'd make it difficult to log in.
Darren

Why my Startup Manager does not appear when I hold the Option key when starting to boot.

I no longer have the Startup Manager appearing when I hold the Option key when starting to boot.
Instead, the system just boots into whichever OS was last selected in the Startup Disk Preference.
How to get back my Startup Manager so that I can boot up from my external hard disk.
Thank you.

Can you please run the following in terminal and post the output in your reply:
diskutil list; echo; nvram -p | grep boot-args; echo

Starts to boot, shows Apple logo for 2+ minutes, then starts again

Yesterday the computer started to boot up as usual with the 'boot chord', Apple logo, then the screen went black, and started over again. This time it successfully booted and ran normally for the rest of the day. This morning, it never gets beyond the boot process; i.e. start chord, Apple logo for several minutes, then black screen and the whole process repeats over and over again. Front panel status LED is on and steady. I tried 5 different boot disks (internal HD, two external SuperDuper clones, a DiskWarrior DVD and the OSX 10.6 install disk and the results were the same. It is still under extended warranty, but I can't afford the downtime for Apple to repair it. Any idea what might be wrong? Any thing else I might try to get it going again?

Hopefully the Time Machine backup is intact and the computer will continue to work with it connected (requires a 3rd party eSATA RAID controller card). Assuming all the hardware works, I am unclear how best to restore the app's from the TM backup.
The official way to do a full restore from TM is to boot from an installation DVD and select "Restore from Time Machine" from the Utilities menu. I don't see how that will work if your backup is on a third-party RAID, because the controller requires a driver that isn't on the DVD. That may be why you can't boot from the DVD.
I think your best bet is to clone the installation disc to a bootable volume and install the RAID driver on it. The volume could be hosted on an external storage device or burned to a DVD. See here for an example of how to do this.

When I turn on my macbook air, it starts to boot and then stops and turns off. How do I fix this?

When I try to turn my MacBook Air on, it starts to boot (gray screen with Apple logo and the swirling indicator) but then it simply shuts off. I have tried Safe Booting but that doesn't work either.
Does anyone have a suggestion as I really need to get a couple of files off the hard drive.

The progress bar on the apple screen indicates that the machine is attempting to boot to safe mode.
Boot your mac and holds down the Option key to boot to the boot manager.
Once in the boot manager click on macintosh HD and click the arrow to boot, this should boot your machine normally.
Also perform an SMC/PRAM reset:
SMC RESET:
Shut down the computer.
Plug in the MagSafe power adapter to a power source, connecting it to the Mac if its not already connected.
On the built-in keyboard, press the (left side) Shift-Control-Option keys and the power button at the same time.
Release all the keys and the power button at the same time.
Press the power button to turn on the computer.
Note: The LED on the MagSafe power adapter may change states or temporarily turn off when you reset the SMC.
PRAM RESET:
Shut down the computer.
Locate the following keys on the keyboard: Command, Option, P, and R. You will need to hold these keys down simultaneously in step 4.
Turn on the computer.
Press and hold the Command-Option-P-R keys. You must press this key combination before the gray screen appears.
Hold the keys down until the computer restarts and you hear the startup sound for the second time.
Release the keys.
If these fail, insert your OSX dvd, boot to boot manager, click the disc, reinstall the mac OSX.

[SOLVED]How to configure pptp vpn start on boot with netcfg?

I've configured 2 profiles:
eth0 and ppp0, where ppp0 is a pptp vpn tunnel.
$ ls /etc/network.d/
eth0 examples interfaces ppp0
$ cat /etc/network.d/ppp0
CONNECTION='ppp'
INTERFACE='ppp0'
PEER='dxt'
PPP_TIMEOUT=10
$ cat /etc/conf.d/netcfg
# Enable these netcfg profiles at boot time.
# - prefix an entry with a '@' to background its startup
# - set to 'last' to restore the profiles running at the last shutdown
# - set to 'menu' to present a menu (requires the dialog package)
# Network profiles are found in /etc/network.d
NETWORKS=(eth0 ppp0)
# Specify the name of your wired interface for net-auto-wired
WIRED_INTERFACE="eth0"
# Specify the name of your wireless interface for net-auto-wireless
WIRELESS_INTERFACE="wlan0"
Manually, I can start up ppp0 correctly.
$ sudo netcfg -u ppp0
:: ppp0 up [ BUSY ] Using interface ppp0
Connect: ppp0 <--> /dev/pts/3
CHAP authentication succeeded
MPPE 128-bit stateless compression enabled
Cannot determine ethernet address for proxy ARP
local IP address 10.100.3.132
remote IP address 10.100.3.1
[ DONE ]
$ ip addr list dev ppp0
8: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1496 qdisc pfifo_fast state UNKNOWN qlen 3
link/ppp
inet 10.100.3.132 peer 10.100.3.1/32 scope global ppp0
But after booting, only eth0 is up. How to configure ppp0 to start on boot with netcfg?
Last edited by rchiang (2012-12-21 01:09:32)

Thanks a lot for your instruction.
netcfg works now!
chris_l wrote:
Did you
systemctl enable [email protected]

Weblogic Admin and Managed Server start using boot.properties and LDAP Acc.

Hello - Can any one please tell me if Weblogic 10.3.x can be started using boot.properties file and by using a user account from the External LDAP (OID) server?
I have configured the Weblogic server and have added a LDAP authenticator.
The Group in OID is mapped to the Admin role in Weblogic so that the user can start and stop the server.
LDAP users can successfully authenticate and access WLS console.
We would like to remove Default Authenticator (Embeded LDAP) from the list of available providers for our security releam.
Thank you.

Tested and got it worked.

Ssh does not start at boot

Hi All
As my title explains, ssh does not start when I reboot.
I can start it like: ./usr/lib/ssh/sshd
So my question is: how can I change this behaviour and let ssh start at boot ?
Thanks a lot in advance
Luca

thnx a lot!!!!
Luca

Windows does not start at boot

Hello,
Windows does not start at boot, how? 'Safe Mode either )

If your system is not properly booting then you must press F8 when start the system then there are two option
Repair Window,start window normally if not properly work then you will install again operating system.

Macbook air shuts down after starting to boot up

My mac book air starts to boot up (the wheal starts to turn for about 30s) than it just turns of
it was working fine a few hours ago, i did a hardware test (every thing was OK) and after that the problem occurred
PRAM Reset did't help
Message was edited by: Zabranjeni

Get a USB external DVD drive, boot from your install disc and try repairing the drive with your Disk Utility. If that does not work, try DiskWarrior, short of reformatting the drive and losing all your data.
Dave M.
MacOSG v.2.0 coming April 1, 2010! No fooling! Check it out!
 MacOSG: An Apple User Group  iTunes: MacOSG Podcast  Follow us on Twitter: MacOSG

My Pavilion DMT-1000 shuts down immediately when it starts to boot up.

HP Paviliion DM4T-1000 running Windows 7 shuts down as soon as it starts to boot up. It passes the startup tests, but it shuts down after about an hour doing the hard disk test. It also shuts down from the boot menu after about an hour. The fan is running full speed at all times and the airflow is perfectly good. I have tried reinitiating the BIOS by removing the internal battery and doing a hard reboot. I have tried booting off of a CD and using the F11. Everything results in immediate shut down. Should the fan be running full speed immdediately? How can I tell if the BIOS thinks the temperature is too high? Is there a test point to monitor? What else can cause a failure to boot?

With the limited information you have provided, look at this comprehensive troubleshooting document:
https://discussions.apple.com/docs/DOC-3353
Ciao.

[SOLVED - partly] Minidlna won't start on boot, but OK otherwise

I am using an up-to-date system as of 2012-11-13. The problem is that minidlna fails to start on boot:
minidlna.service - minidlna server
Loaded: loaded (/usr/lib/systemd/system/minidlna.service; enabled)
Active: failed (Result: exit-code) since Tue, 2012-11-13 07:53:55 CET; 1h 33min ago
Process: 401 ExecStart=/usr/sbin/minidlna -P /var/run/minidlna/minidlna.pid (code=exited, status=255)
CGroup: name=systemd:/system/minidlna.service
Nov 13 07:53:59 earth minidlna[401]: [2012/11/13 07:53:54] minidlna.c:754: fatal: No IP address automatically detected!
So I guess it has to do something with the network, I am using DHCP, with systemd + net-auto-wired.service.
I have found this: https://ask.fedoraproject.org/question/ … r-dhcp-has
They have solved the problem by changing the after part in the unit by adding: dbus-org.freedesktop.NetworkManager.target
Since I do not use networkmanager, this is not an option for me. The current, unmanipulated state of the minidlna unit is:
[Unit]
Description=minidlna server
After=network.target
[Service]
Type=forking
User=nobody
ExecStart=/usr/sbin/minidlna -P /var/run/minidlna/minidlna.pid
PIDFile=/var/run/minidlna/minidlna.pid
[Install]
WantedBy=multi-user.target
What I have noticed is that it refers to a network.target in the after section, but it seems to me that I don't have one.
I only have:
UNIT LOAD ACTIVE SUB JOB DESCRIPTION
basic.target loaded active active Basic System
cryptsetup.target loaded active active Encrypted Volumes
getty.target loaded active active Login Prompts
graphical.target loaded active active Graphical Interface
local-fs-pre.target loaded active active Local File Systems (Pre)
local-fs.target loaded active active Local File Systems
multi-user.target loaded active active Multi-User
remote-fs.target loaded active active Remote File Systems
sockets.target loaded active active Sockets
sound.target loaded active active Sound Card
swap.target loaded active active Swap
sysinit.target loaded active active System Initialization
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
JOB = Pending job for the unit.
12 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
Edit: having run the command again with the --all prefix:
Notice: network.target loaded inactive dead Network
UNIT LOAD ACTIVE SUB JOB DESCRIPTION
basic.target loaded active active Basic System
cryptsetup.target loaded active active Encrypted Volumes
emergency.target loaded inactive dead Emergency Mode
final.target loaded inactive dead Final Step
getty.target loaded active active Login Prompts
graphical.target loaded active active Graphical Interface
local-fs-pre.target loaded active active Local File Systems (Pre)
local-fs.target loaded active active Local File Systems
multi-user.target loaded active active Multi-User
network.target loaded inactive dead Network
nss-lookup.target loaded inactive dead Host and Network Name Lookups
nss-user-lookup.target loaded inactive dead User and Group Name Lookups
remote-fs.target loaded active active Remote File Systems
rescue.target loaded inactive dead Rescue Mode
shutdown.target loaded inactive dead Shutdown
sockets.target loaded active active Sockets
sound.target loaded active active Sound Card
swap.target loaded active active Swap
sysinit.target loaded active active System Initialization
syslog.target loaded inactive dead Syslog
umount.target loaded inactive dead Unmount All Filesystems
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
JOB = Pending job for the unit.
21 loaded units listed.
To show all installed unit files use 'systemctl list-unit-files'.
My question is what should I add to the after part to make minidlna work upon booting? Wouldn't a graphical.target be an overkill?
Thanks in advance.
Last edited by szebenyib (2012-12-02 16:45:26)

szebenyib wrote:(However I cannot access the internet that way, maybe because of a bad network file. Honestly I have some space to improve my network knowledge.)
In the case of the possible bad network file. here is what it expects. First, you need to know the router's IP address. In the following I will assume 192.168.0.1 for the router's IP address.
192.168.0.1 is common for D-Link routers, but it does vary by router manufacturer and model. I believe 192.168.1.1 is common for Linksys.
/etc/conf.d/network
interface=eth0 # ethernet port to activate, usually eth0
address=192.168.0.110 # IP address you want the minidlna computer to have. the first 3 triads must be the same as the router's IP addr in this case 192.168.0 the fourth triad can be from 5 to 250
netmask=24
broadcast=192.168.0.255 # the first 3 triads must be the same as the router's IP address and the fourth triad should be 255
gateway=192.168.0.1 # the IP address of your router
In a terminal window, enter:
systemctl restart network.service
ping -c5 127.0.0.1
which is localhost. The -c5 means ping 5 times then quit. If you get: 5 packets transmitted, 5 received, 0% packet loss then the ping was successful, which means
that the ethernet port (usually eth0) is active. If this ping is not successful, go back and check the syntax and spelling in both /etc/conf.d/network and /etc/systemd/system/network.service
If the ping is successful:
ping -c5 192.168.0.1
and ping the router.
If you cannot ping the router's IP address, then there is still something wrong in one of the two involved files. or the router's settings need to be changed.
If you can ping the router's IP address successfully and still cannot get to the internet, you probably have DNS server issues.
ping -c5 google.com
ping -c5 8.8.8.8
If you cannot ping google.com but can ping 8.8.8.8 then you have DNS problems, see Arch WIKI resolv.conf
My network is a mixture of DHCP and STATIC IP addresses. In my router, I have the DHCP server enabled to give IP addresses between 192.168.0.10 and 192.168.0.60
this gives the router 50 DHCP addresses to work with which is more that enough for my home network. The rest of the addresses between 192.168.0.61 and 192.168.0.250
can be used as static addresses. Just an example, this can be changed as necessary.
HTH
Pudge

Auditing a process started at boot time

Hi All,
I am having a problem with auditd. I am starting a process of my own at boottime that I would like to audit. I think the problem lies in that my process is not getting an auditID. If I run the process from a terminal after the system is started it audits correctly, only when started at boot will it not audit.
I have the process's audit class defined in the audit_control file as such (md is my audit class):
dir:/var/audit
flags:md,lo,ad,-fw,-fm,-fd,-nt,no
minfree:50
naflags:md
I thought placing it under naflags would allow it to audit without attributes, but this does not work. The audit event and audit class are also properly in place.
Any help with getting a process to audit when started at boot would be greatly appreciated.
Victor

Hi,
Processes, are not able to start at boot-time as the "processes" is a OS based concept. The closest method you can do is replace the bootloader of Windows with your bootloader then load the Windows through your bootloader, and before loading the OS your
Bootloader can perform any calculations or start files up as soon as Windows loads. This is the only way to start processes closest to Boot time.
In windows vista+ OS this technique would not work because Windows Vista+ has Session separation which by design separates processes into sessions and if you were to start it as soon as the OS starts the process would crash the entire OS as the process would
not be able to fit in any session as it started before "Winlogon.exe"
process. Therefore it is not really possible.

[solved] wireless doesn't start at boot

I have BCM94311MCG wlan mini-PCI (rev 01) which works with b43 + wpa_supplicant nicely, except I can't seem to get to automagically start at boot time.
wlan0 always times out (wired connects at boot time just fine). I'd like my laptop to automatically connect to one of two networks, else remain disconnected.
Once started I can always netcfg2 <network name> and it connects no problem... I must have missed something in the wireless setup but I can't find what it is.
my rc.conf:
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
LOCALE="en_US.utf8"
HARDWARECLOCK="localtime"
USEDIRECTISA="yes"
TIMEZONE="Canada/Pacific"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
MOD_AUTOLOAD="yes"
MOD_BLACKLIST=(!pcspkr !bcm43xx !ndiswrapper ) #deprecated
MOD_LOADLIST=(acpi-cpufreq cpufreq_ondemand slhc i8k tg3 fuse b43 ppdev snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore)
MODULES=( ${MOD_BLACKLIST[@]} ${MOD_LOADLIST[@]} )
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
HOSTNAME="myhostname"
# Interfaces to start at boot-up (in this order)
eth0="dhcp"
wlan0="dhcp"
INTERFACES=(eth0 wlan0)
# Routes to start at boot-up (in this order)
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
NETWORKS=("auto-wireless wlan0")
# DAEMONS
DAEMONS=(syslog-ng iptables @network @fusesmb @cups !netfs !crond @alsa @hal @dbus @fam @acpid @laptop-mode @cpufreq)
afaik the only unique thing I have in rc.conf is my fusesmb daemon (a script that mounts samba shares)
and my network.d/<network name>
CONNECTION="wireless"
INTERFACE=wlan0
SCAN="yes"
SECURITY="wpa-config"
ESSID="BCSI"
IP="dhcp"
TIMEOUT=20
when I look for wpa_supplicant after a boot, it is not running ( ps aux | grep wpa ).
wlan0 is up right after boot:
$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:15:C5:08:1E:1C
inet addr:10.1.1.148 Bcast:10.1.1.255 Mask:255.255.255.0
inet6 addr: fe80::215:c5ff:fe08:1e1c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:14443 errors:0 dropped:0 overruns:0 frame:0
TX packets:13281 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:8031647 (7.6 Mb) TX bytes:2248854 (2.1 Mb)
Interrupt:19
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1221 errors:0 dropped:0 overruns:0 frame:0
TX packets:1221 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:75880 (74.1 Kb) TX bytes:75880 (74.1 Kb)
wlan0 Link encap:Ethernet HWaddr 00:16:CE:67:85:B5
inet addr:169.254.55.57 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
wmaster0 Link encap:UNSPEC HWaddr 00-16-CE-67-85-B5-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
but since wpa_supplicant isn't running, it won't associate.
I'm misunderstading (I think) how netcfg2 is used during startup, I thought the line `NETWORKS=("auto-wireless wlan0")` would tell netcfg2 to try /etc/network.d/*
thanks for looking
Last edited by bioe007 (2008-04-30 14:19:12)

From: http://wiki.archlinux.org/index.php/Network_Profiles
"Ensure that net-profiles is in your rc.conf DAEMONS=() line."

Openntpd won't start at boot [SOLVED]

Hi all!
My system clock is perpetually off by 4 hours, and I've narrowed it down to an issue with Openntpd; it seems to be refusing to start at boot time. Here are the relevant lines from daemon.log:
Sep 1 21:30:26 raskolnikov ntpd[1440]: Terminating
and the output of ps aux | grep ntpd:
[raskolnikov@raskolnikov ~]$ ps aux | grep ntpd
ntp 1323 0.0 0.0 3184 700 ? S 17:32 0:00 /usr/sbin/ntpd -s
root 1332 0.0 0.0 3292 256 ? Ss 17:32 0:00 /usr/sbin/ntpd -s
1000 1412 0.0 0.0 3616 800 pts/0 S+ 17:33 0:00 grep ntp
I can manually restart the daemon via /etc/rc.d/openntpd restart, which works fine, and the time is set correctly. However, when I reboot, the adjustments are wiped out, and the daemon does not start again (same message in daemon.log). I have the default ntpd.conf. I have found very little helpful information on Google, I would greatly appreciate it if someone could point me in the right direction, I've wasted quite a few hours this evening working on this problem! Thanks!
Edit: Just in case it's helpful, here is my daemons array from rc.conf:
DAEMONS=(syslog-ng !network acpid eee hal networkmanager netfs crond openntpd bitlbee)
Last edited by happycodemonkey (2009-09-02 03:55:46)

I've had this problem too, although I do not use networkmanager. I've found that openntpd fails to configure itself properly if the network is not up when it starts (in my case this happens when I background the network daemon and start openntpd in the daemons array).
My current working solution* is to add this line to rc.local:
(sleep 300 && /etc/rc.d/openntpd start) &
That will wait 5 minutes before starting the openntpd daemon which gives the network more than sufficient time to start. An alternative would be run "/etc/rc.d/openntpd restart" in an hourly cronjob if your network settings change often.
* Why not just unbackground the network daemon you ask? If the network isn't up then it takes a while to timeout and I don't want to wait to boot in that case.
Last edited by Xyne (2009-09-02 02:05:52)

OVI starts on boot up

Similar Messages

Maybe you are looking for