Moving of /var/run/daemons to /run/daemons

Hi, just curious here. Why was the location of the "daemons" files representing running daemons moved from /var/run/daemons to /run/daemons ?
I note this happened around April 9th.
(http://mailman.archlinux.org/pipermail/ … 00576.html)
Was there a problem with the original location?
Just interested.
Cheers.

It's because /run is mounted as a tmpfs so it has write access at any time during the boot process which isn't the case with /var. It fixes some problems.

Similar Messages

  • "netcfg2 -a" does not remove "/var/run/daemons/net-profiles"

    hello!
    i have found out, that a "netcgf2 -a" does not remove /var/run/daemons/net-profiles. after that i have to stop the net-profiles daemon by hand. i connect to networks with "netcfg2 <profile>", the net-profiles daemon will be started automatically by that command.
    is this an issue?
    another problem i have is, that netcfg2 even cannot connect to a network automatically, if i have two networks with the same beginning:
    for example: network a: foo; network b: foobar - when i want to connect to "foo" it uses the "foobar" profile, because the name of the profile file is listed before the name of the file from network a.
    bye iggy

    The first thing: I thing netcfg2 should not touch anything in /var/run/daemons, since that's the job of scripts in /etc/rc.d/* It's the same for any daemon you run - if you kill it manually, not using /etc/rc.d/<whatever> stop, then you have to clean up /var/run/daemons/<whatever> yourself as well.
    before connecting with netcfg2 there is no "net-profiles" in /var/run/daemons. after netcfg2 <profile> it is. after "netcfg2 -a" the file is still there, so it indicates net-profiles-daemon is still running.
    Last edited by iggy (2008-05-06 13:52:28)

  • GW POA Can't write .pid file to var/run/novell/groupwise

    I'm running GW 8.0.2 HP2 on SLES 10, and just recently figured out after trying to set up a CRON job that I can't restart my POA without rebooting the server. When I run a rcgrpwise status, the POA shows as "unused." Running rcgrpwise stop or restart fails to stop the POA, though the domain goes up and down with no issue. I've checked my gwha.conf file, and everything appears to be in the correct case, and referencing the correct locations. The domain can create its .pid file in /var/run/novell/groupwise just fine.....
    I've read and followed the directions in the tid 7003322 (which sounded like a direct match for this issue), but when I edit the header for the POA an rcgrpwise status returns that it is "unable to check [@gw4post.poa]"
    The forum thread titled: "rcgrpwise status shows "unused", but it is running." also sounds like the same problem, but there was no resolution.
    Anyone have any ideas? Please let me know if I can provide any further informnation - I'm writing this at 0-dark-30 and probably left something out....
    Thanks,
    Stacey

    Okay, so your stuff looks good.
    Yes, when the system boots it's supposed to basically load/fire up the rcgrpwise script (more or less, but it reads the gwha.conf file)
    That is quite odd that if you bounce the server, it's fine.
    Greg is correct that the PID file(s) get written to the directory where your log files are at.
    Do you know where you log directories are at for the MTA/POA?
    They should be in diff. directories.
    Brief section from the docs:
    If you selected Launch GroupWise Agents on System Startup in the Installation program, the Installation program configured your system so that the agents start automatically each time you restart your server. The Agent Installation programs always creates a grpwise startup script in /etc/init.d for starting the agents, as described in Starting the Linux GroupWise Agents as Daemons. To enable automatic startup, the Agent Installation programs also create symbolic links named Snngrpwise in the rc3.d and rc5.d directories so that the agents load on restart into level 3 or 5, depending on the configuration of your Linux system. The value of nn is determined by the chkconfig command during installation so that the GroupWise agents are started in the proper sequence with other processes running on the server.
    When the grpwise script runs and starts the GroupWise agents, the agents read the agent startup files in /opt/novell/groupwise/agents/share to check for configuration information provided by startup switches. Because the --show switch cannot be used in the startup files, the agents do not run with server console interfaces when started automatically when the server restarts, unless you modify the gwha.conf file as described in Enabling the High Availability Service for the Linux GroupWise Agents.

  • [solved] /var/run/dbus/pid

    After Crashing my System with the kernel Update Yesterday, I set up a new clean Installation.  I got now this error message at the start up screen.
    Failed to start message bus : The pid file "/var/run/dbus/dbus.pid" ...
    I don't understand what I have to do!
    Last edited by JaDa (2007-08-24 03:02:12)

    Doehni wrote:I think this could be a problem with the order your daemons are started. Is dbus already started by another daemon before this message comes?
    @Doehni
    You give me the Idea! Thank's a lot
    no how I solved the problem
    vi /etc/rc.conf
    before
    DAEMONS=( hal dbus ........)
    then changed to
    DAEMONS=(...... dbus hal ......)
    and the problem was solved
    Last edited by JaDa (2007-08-24 03:09:05)

  • Error: Can't connect to auth server at /var/run/dovecot/auth-master: No su

    Error: Can't connect to auth server at /var/run/dovecot/auth-master: No such file or directory
    error showing up, there is no auth-master file in /var/run/dovecot
    this has just happnened over night
    any ideas how to re-install dovecot
    google search goes on about linux but barely any info about max osx server

    auth-master is created when you start the mail service. Deleted if you stop the mail service. If that is not happening, you may have to re-install mail. Dovecot is the IMAP/POP part of the mail service. I am not sure what happens if you disable IMAP. I am guessing it is not there. But that is the extent of any tips I can offer. I suppose you could reinstall, but that seems a bit extreme to me.

  • Database error #2002 can not connect local mysql server to socket through '/var/run/mysqld/mysqld.sock'(2) on mac os x 10.9.2

    Dear Fellas:
    I received "database error #2002 can not connect local mysql server to socket through '/var/run/mysqld/mysqld.sock'(2)" on mac os x 10.9.2.
    mysql info:
    ps -ef | grep mysql
        0    66     1   0 11:06AM ??         0:00.04 /bin/sh /usr/local/mysql/bin/mysqld_safe --user=mysql
       74   225    66   0 11:06AM ??         0:02.50 /usr/local/mysql/bin/mysqld --basedir=/usr/local/mysql --datadir=/usr/local/mysql/data --plugin-dir=/usr/local/mysql/lib/plugin --user=mysql --log-error=/usr/local/mysql/data/Chuans-MacBook-Pro-2.local.err --pid-file=/usr/local/mysql/data/Chuans-MacBook-Pro-2.local.pid --socket=/var/run/mysqld/mysqld.sock
      501   952   947   0  3:52PM ttys000    0:00.00 grep mysql
    Please help!!

    Fascinated and guessing:
    Something related to sock(2) because that's not part of your copied info. I'm thinking you've doubled up on sockets and the second socket doesn't exist, meaning you should be connecting to the first socket "mysqld.sock" whether automatic or not.
    I've only used GUI tools on purpose, so does this mean you've already got MySQL running and you tried to launch it again manually? Perhaps you already have one instance of a db and you're trying to launch a second instance, and the two can't coexist with a single user local db?
    Assuming this is all local, I'd shut down the db service and restart it, out of hand. I've seen similar messages when I set the db to start up on boot, and it didn't finish shutting down when I tried to restart it manually. Usually the GUI won't let me turn it on because it reports it's already running, but in that case it hadn't finished performing what the GUI was reporting.
    Just speculating.

  • /var/run symlink replaced by directory after reboot

    Hi guys!
    I have installed Arch on my home server a few days ago using the latest (2012.06) iso available (not the net install).
    My boot, root and swap partitions are all mdadm raid 1 and i use syslinux to boot which works fine.
    After setting up my machine for a while i noticed the "filesystem" package was not properly installed by pacstrap (even though it's already pretty old and should be included in the latest iso). Don't get me wrong it WAS installed, but only the /var/lock directory was symlinked. As most of you know this package update should replace /var/run and /var/lock with symlinks.
    So i just tried to "reinstall" this package with 'pacman -S filesystem --force' (as described in the news post).
    At first it looked great - symlinks were there and i could start several services with systemctl (which didn't work for a lot of services before), but get this:
    After every reboot or simply after some time the symlink (just of /var/run , not lock) was GONE and a file (not directory) "run" gets created with the following permissions - -rw------- root root. What happens is that at every reboot systemd-logind dbus and therfor most other stuff won't get started properly. For example after boot i had only just the terminal at F1, all other screens were just black and after some time i get the message that systemd-logind.service failed.
    When i manually remove the file and replace it by the symlink i can manually start/restart all services and from that time on everything works great.
    What i was interested in was WHAT exactly removed my symlink after some time or at boot time, so i used audit to monitor the symlink for  a while.
    Here's what i got when the symlink was removed and then a file "run" was "touched": http://pastebin.com/BYsRHWbC
    Unfortunately the ppid ( i guess "parent process id") was not running anymore so i still don't have any idea what's going on exactly.
    I'd appreciate ANY information or tip you have. My guess is that systemd is involved somehow.
    As a sidenote: Before i found out the symlink was missing i installed initscripts once to see of systemd was just still buggy. I removed it shortly after though.
    Looking forward to input and I'm happy to answer your questions.
    Last edited by Guybrush (2012-10-25 17:19:49)

    Isn't Shorewall is just a collection of scripts that load iptables rules? Even the Shorewall binary is just a shell script, so you can easily `grep` through it and the config/helper files that make up Shorewall to see what it's up to.
    Looks like the only time it messes with `touch` is here:
    root@antec /etc/shorewall# grep -R touch /usr/share/shorewall/*
    /usr/share/shorewall/prog.footer: touch $STARTUP_LOG
    /usr/share/shorewall/prog.footer: [ -n "$SUBSYSLOCK" ] && touch $SUBSYSLOCK
    /usr/share/shorewall/prog.footer: [ $status -eq 0 ] && touch $SUBSYSLOCK || rm -f $SUBSYSLOCK
    /usr/share/shorewall/prog.footer: [ $status -eq 0 ] && touch $SUBSYSLOCK || rm -f $SUBSYSLOCK
    So.. maybe your shorewall.conf file has set SUBSYSLOCK to something invalid, like /var/run, and it's wiping it out each time when it checks for the PID lock file?
    I was able to get Shorewall to run and put its PID file in SUBSYSLOCK=/var/lock/shorewall
    It didn't mess with /run or /var/run at all.
    Had to change the systemd 'shorewall.service' file quite a bit though. It's not correct at all.

  • Shared memory in /var/run instead of /tmp

    I use shared memory segment on a diskless node.
    This shared memory segment are stored in /tmp.
    Is there a way to put them in a "memory based" directory, as /var/run (solaris 8) instead of
    the disk-based directory

    My problem was especially to change toe location
    of the shared memory on file system. I succeed
    with FIFO but not with shared memory. I
    don't find any solution.
    concerning the definition of memory base vs. file
    based I have no clue but the following extract from
    docset
    ------[Extract from solaris 8 documentation]-----
    The /var/run File System
    A new TMPFS-mounted file system, /var/run, is the
    repository for temporary system files that are not
    needed across system reboots in this Solaris release
    and future releases. The /tmp directory continues to
    be repository for non-system temporary files.
    Because /var/run is mounted as a memory-based file
    system rather than a disk-based file system, updates
    to this directory do not cause unnecessary disk
    traffic that would interfere with systems running
    power management software.
    The /var/run directory requires no administration.
    You may notice that it is not unmounted with the
    umount -a or the umountall command.
    For security reasons, /var/run is owned by root.

  • Correct entry for /var/run/slapd.pid

    what is the correct pid for slapd?
    my os x did not come with slapd.pid so I'm
    trying to create one manually, but I don't
    know what I'm supposed to use.
    also any one know the correct entry for
    /var/run/slapd.args?
    Thanks,
    Tadashi

    what is the correct pid for slapd?
    my os x did not come with slapd.pid so I'm
    trying to create one manually, but I don't
    know what I'm supposed to use.
    When slapd is running it saves its pid in the file /var/run/slapd.pid
    This allows other processes to find its pid to use to communicate with it.
    You do not need to create this file.
    also any one know the correct entry for
    /var/run/slapd.args?
    Similar to above, this is created by slapd. You don't need to worry about it.
    The better question is why is slapd not running (assuming your machine is set up to be an OD Master).
    HTH
    - Leland

  • Can you keep your playlist when moving from computer running xp to computer running vista.          v

    can you keep your playlist when moving from computer running xp to computer running vista as i keep losing my playlists when using computer with vista running on it.ipod touch 3rd gen set up originally on computer running xp.thanks.

    This seems to be a commercial product. For the best chance at finding a solution I would suggest posting in the forum for HP Business Support!
    You can find the Commercial Laserjet board here:
    http://h30499.www3.hp.com/t5/Printers-LaserJet/bd-p/bsc-413
    Best of Luck!
    You can say thanks by clicking the Kudos Star in my post. If my post resolves your problem, please mark it as Accepted Solution so others can benefit too.

  • /var/run/name_service_door - zones stuck in single user mode

    Hello,
    I have two Sol10 boxes - e4500 & x86. Both have multiple zones configured which have been working for quite a while. I was enabling audit logging on these machines (perzone) which required a reboot.
    After a reboot, the zones won't come out of the singleuser milestone. Trying to ping the global zone by name (nsswitch is files, dns), it hangs. A truss reveals:
    open64("/var/run/name_service_door", O_RDONLY) = 3
    fcntl(3, F_SETFD, 0x00000001) = 0
    door_info(3, 0xFF16F7A8) = 0
    door_call(3, 0xFFBFD790) (sleeping...)
    and hangs forever.
    I threw the latest patch cluster at both and it had no effect.
    Each zone has a /etc/sysidcfg, /etc/.NFS4inst_state.domain, and proper nsswitch.conf/resolv.conf that had been working (rebooting) until I tried to enable auditing. This happened a while ago and a total uninstall/reinstall of the zones fixed the issue.
    svcs reveals
    offline 13:11:49 svc:/network/nfs/client:default
    offline 13:11:49 svc:/system/filesystem/autofs:default
    offline 13:11:49 svc:/system/system-log:default
    offline 13:11:49 svc:/network/smtp:sendmail
    offline 13:11:49 svc:/milestone/multi-user:default
    offline 13:11:49 svc:/milestone/multi-user-server:default
    offline 13:11:50 svc:/application/print/ipp-listener:default
    offline 13:11:53 svc:/network/ssh:default
    #svcadm milestone svc:/milestone/multi-user:default
    Requesting System Maintenance Mode
    (See /lib/svc/share/README for more information.)
    Console login service(s) cannot run
    Root password for system maintenance (control-d to bypass):
    At this point I'm not sure how to debug this issue. Any ideas?
    Thanks
    Zetan

    Hi, snikpmup.
    Your panic log cites a page fault:
    panic(cpu1 caller 0x001A3135): Unresolved kernel trap (CPU 1, Type 14=page fault)…
    This is a common fault type, indicating the processor could not access either data memory or the next instruction to be executed. Potential causes include RAM problems, hard disk corruption, and programming errors.
    The panic log you posted is incomplete, so there's not much else to say based on what you've posted. I do note some messages prior to the panic indicating M-Audio devices: you might want to check with those folks re: Mac Pro compatibility, any necessary updates, etc.
    I suggest following the full set of troubleshooting steps cited in my "Resolving Kernel Panics" FAQ. The FAQ includes step-by-step instructions for identifying and resolving some of the most common causes of kernel panics. The FAQ is a roadmap: start at the beginning and work systematically through the end, i.e. the "If all else fails..." section.
    Good luck!
    Dr. Smoke
    Author: Troubleshooting Mac® OS X
    Note: The information provided in the link(s) above is freely available. However, because I own The X Lab™, a commercial Web site to which some of these links point, the Apple Discussions Terms of Use require I include the following disclosure statement with this post:
    I may receive some form of compensation, financial or otherwise, from my recommendation or link.

  • /var/run space

    Solaris 10 on a T1000
    Why can't I load this kernel patch? I seem to have lots of space.
    #patchadd 120011-14
    Unable to install patch. Not enough space in /var/run to copy overlay objects.
    154MB needed, 65MB available.
    root# df -h
    Filesystem size used avail capacity Mounted on
    /dev/dsk/c0t0d0s0 11G 7.1G 3.3G 69% /
    /devices 0K 0K 0K 0% /devices
    ctfs 0K 0K 0K 0% /system/contract
    proc 0K 0K 0K 0% /proc
    mnttab 0K 0K 0K 0% /etc/mnttab
    swap 8.1G 1.2M 8.1G 1% /etc/svc/volatile
    objfs 0K 0K 0K 0% /system/object
    /platform/SUNW,Sun-Fire-T1000/lib/libc_psr/libc_psr_hwcap1.so.1
    11G 7.1G 3.3G 69% /platform/sun4v/lib/libc_psr.so.1
    /platform/SUNW,Sun-Fire-T1000/lib/sparcv9/libc_psr/libc_psr_hwcap1.so.1
    11G 7.1G 3.3G 69% /platform/sun4v/lib/sparcv9/libc_psr.so.1
    fd 0K 0K 0K 0% /dev/fd
    /dev/dsk/c0t0d0s5 5.8G 3.0G 2.7G 53% /var
    swap 8.1G 72K 8.1G 1% /tmp
    swap 8.1G 48K 8.1G 1% /var/run

    Whenever you install a patch, check the readme for the patch. Use that to determine whether or not to bring the system to single-user mode for patch install.

  • /var/run/resolv.conf auto-regenerate

    Hello,
         for a while, one of my 10.6.8 servers looses its DNS adresses at each reboot and put the old adresses instead.
          When I change it in System Preferences, /var/run/resolv.conf is OK, but after reboot this file is generated with old values.
          NOTE : since last week, it changes them when it is running .
         Any idea would be very appreciated.
    Regards,
    Joan

    Hi dmare,
         thank you for your reply.
         I do not modify resolv.conf directly, I modify DNS IPs in System Preferences > Network which modifies resolv.conf.
         I do that to put correct DNS IPs.
    Joan

  • Shouldn't /var/run and /var/run/lock point to absolute paths?

    I have a setup with my 'var' on a separate partition that causes /var/run and /var/run/lock to point to nothing each time I upgrade the filesystem package and I wonder if this is a bug.
    Mounted at /mnt/data is a luks encrypted partion where I keep my home and var as subdirectories. Two symlinks point to them from root:
    # ls -al /
    lrwxrwxrwx 1 root root 14 Apr 21 2011 home -> /mnt/data/home
    lrwxrwxrwx 1 root root 13 Apr 21 2011 var -> /mnt/data/var
    Each time I upgrade the filesystems package however I end up with /var/run and /var/lock pointing to  '../run' and ../run/lock', which in my case are the non-existing /mnt/data/run and /mnt/data/run/lock.  I have to delete the symlinks and make them link to the absolute  /run and /run/lock. Is there a reason the symlinks are relative instead of absolute?
    [edit]
    (this should have been posted in 'Pacman & Package Upgrade Issues' instead of here.)
    [edit]
    Last edited by rwd (2012-06-24 18:14:08)

    Thanks! After using bind mounts and  reinstalling the filesystems package the relative links work. Still I wonder why using bind mounts instead of symlinks is the 'correct' way. The only advantage I see is to have the ability to use mount options, which In my case I don't need.

  • Mac OS X Lion[360] Can not connect to /var.run/systemkeychaincheck.socket

    I have cleaned my hard disk, and want to install a clean OS X Lion via the Internet, but it shows this error:
    Mac OS X Lion[360] Can not connect to /var.run/systemkeychaincheck.socket
    and the time is still at : remains about 103 hours and 36 mins.

    No, I do not know why.
    I installed a new copy of Lion via USB Flash Installer. I have no iead about how to fix this problem.

Maybe you are looking for