Re: Glitch in Upgrading from EOL Fedora using yum
And I had it showed systemd, dbus-daemon, atd, crond, cupsd, avahi-daemon, rpcbind, and all sorts of other things having open files in /var/run. Nothing was using it as a cwd. So I'm not sure why that would stop it from being renamed. On 05/13/2013 08:12 PM, Christopher Meng wrote: Maybe you can try lsof? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Glitch in Upgrading from EOL Fedora using yum
but *it is not the same filesystem* if you stay on topic and /var is a own partition Am 14.05.2013 18:41, schrieb Philip Prindeville: I get that part… but that shouldn't stop the directory from being renamed if it's staying on the same filesystem. -Philip On May 14, 2013, at 6:08 AM, Björn Esser bjoern.es...@gmail.com wrote: All those have their corresponding .pid-files inside /var/run. So I guess some of them are keeping an open handle on it. Am Montag, den 13.05.2013, 22:45 -0600 schrieb Philip A. Prindeville: And I had it showed systemd, dbus-daemon, atd, crond, cupsd, avahi-daemon, rpcbind, and all sorts of other things having open files in /var/run. Nothing was using it as a cwd. So I'm not sure why that would stop it from being renamed. On 05/13/2013 08:12 PM, Christopher Meng wrote: Maybe you can try lsof? signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Glitch in Upgrading from EOL Fedora using yum
On 05/13/2013 04:29 PM, Philip A. Prindeville wrote: but when I tried this, I get: [root@mail /]# mv -f /var/run /var/run.runmove~ mv: cannot move `/var/run' to `/var/run.runmove~': Device or resource busy [root@mail /]# right off the bat. Anyone know what the workaround is for this? You need to boot a live cd or rescue cd in order to do this. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Glitch in Upgrading from EOL Fedora using yum
All those have their corresponding .pid-files inside /var/run. So I guess some of them are keeping an open handle on it. Am Montag, den 13.05.2013, 22:45 -0600 schrieb Philip A. Prindeville: And I had it showed systemd, dbus-daemon, atd, crond, cupsd, avahi-daemon, rpcbind, and all sorts of other things having open files in /var/run. Nothing was using it as a cwd. So I'm not sure why that would stop it from being renamed. On 05/13/2013 08:12 PM, Christopher Meng wrote: Maybe you can try lsof? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Glitch in Upgrading from EOL Fedora using yum
I get that part… but that shouldn't stop the directory from being renamed if it's staying on the same filesystem. -Philip On May 14, 2013, at 6:08 AM, Björn Esser bjoern.es...@gmail.com wrote: All those have their corresponding .pid-files inside /var/run. So I guess some of them are keeping an open handle on it. Am Montag, den 13.05.2013, 22:45 -0600 schrieb Philip A. Prindeville: And I had it showed systemd, dbus-daemon, atd, crond, cupsd, avahi-daemon, rpcbind, and all sorts of other things having open files in /var/run. Nothing was using it as a cwd. So I'm not sure why that would stop it from being renamed. On 05/13/2013 08:12 PM, Christopher Meng wrote: Maybe you can try lsof? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Glitch in Upgrading from EOL Fedora using yum
I was reading the document: http://fedoraproject.org/wiki/Upgrading_from_EOL_Fedora_using_yum#Fedora_16_-.3E_Fedora_17 and got to the section: If you have /var on a separate partition, you will have to manually convert /var/run and /var/lock to a symbolic link. # mv -f /var/run /var/run.runmove~ # ln -sfn ../run /var/run # mv -f /var/lock /var/lock.lockmove~ # ln -sfn ../run/lock /var/lock but when I tried this, I get: [root@mail /]# mv -f /var/run /var/run.runmove~ mv: cannot move `/var/run' to `/var/run.runmove~': Device or resource busy [root@mail /]# right off the bat. Anyone know what the workaround is for this? Thanks, -Philip -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Glitch in Upgrading from EOL Fedora using yum
Maybe you can try lsof? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Glitch in Upgrading from EOL Fedora using yum
And I had it showed systemd, dbus-daemon, atd, crond, cupsd, avahi-daemon, rpcbind, and all sorts of other things having open files in /var/run. Nothing was using it as a cwd. So I'm not sure why that would stop it from being renamed. On 05/13/2013 08:12 PM, Christopher Meng wrote: Maybe you can try lsof? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
