- Previous thread: Possibly unbuildable ports reminder
- Next thread: IBM T43 - iwi0 firmware stuck issue
- Threads sorted by date: freebsd 200906
Hi,
What are stale lock files?
I've been having them for a few weeks now, they need to go away!
root@curly /root# portupgrade -a
** Stale lock file was found. Removed.
** Stale lock file was found. Removed.
[...]
root@curly /root# portversion -c
** Stale lock file was found. Removed.
#
# p5-BerkeleyDB
# needs updating (port has 0.39)
#
pkgs="$pkgs p5-BerkeleyDB-0.38"
#
# portaudit
# needs updating (port has 0.5.13)
#
pkgs="$pkgs portaudit-0.5.12"
#
# ruby
# needs updating (port has 1.8.7.160_3,1)
#
pkgs="$pkgs ruby-1.8.7.160_1,1"
if [ X"$pkgs" != X"" ]; then
portupgrade "$@" $pkgs
fi
Thanks,
Charles
--
Pretty women make us BUY beer. Ugly women make us DRINK beer. - Al Bundy
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
What are stale lock files?
I've been having them for a few weeks now, they need to go away!
root@curly /root# portupgrade -a
** Stale lock file was found. Removed.
** Stale lock file was found. Removed.
[...]
root@curly /root# portversion -c
** Stale lock file was found. Removed.
#
# p5-BerkeleyDB
# needs updating (port has 0.39)
#
pkgs="$pkgs p5-BerkeleyDB-0.38"
#
# portaudit
# needs updating (port has 0.5.13)
#
pkgs="$pkgs portaudit-0.5.12"
#
# ruby
# needs updating (port has 1.8.7.160_3,1)
#
pkgs="$pkgs ruby-1.8.7.160_1,1"
if [ X"$pkgs" != X"" ]; then
portupgrade "$@" $pkgs
fi
Thanks,
Charles
--
Pretty women make us BUY beer. Ugly women make us DRINK beer. - Al Bundy
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
On Sat, 27 Jun 2009 10:00:24 -0500, Charles Howse wrote:
> What are stale lock files?
> I've been having them for a few weeks now, they need to go away!
Lock files are used by several programs to indicate file-wise that
they are running. The lock file is created when the program starts,
and usually deleted when it ends. If it is interrupted (due to an
error or ^C), the lock file isn't removed.
Most programs remove stale lock files by theirselves when they are
started again (e. g. fetchmail).
It's possible that there are programs that refuse to start, because
the lock file (falsely) indicates that the program is already running.
The location of the lock file seems to depend on the respective
program.
--
Polytropon
>From Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
> What are stale lock files?
> I've been having them for a few weeks now, they need to go away!
Lock files are used by several programs to indicate file-wise that
they are running. The lock file is created when the program starts,
and usually deleted when it ends. If it is interrupted (due to an
error or ^C), the lock file isn't removed.
Most programs remove stale lock files by theirselves when they are
started again (e. g. fetchmail).
It's possible that there are programs that refuse to start, because
the lock file (falsely) indicates that the program is already running.
The location of the lock file seems to depend on the respective
program.
--
Polytropon
>From Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
Charles Howse writes:
> What are stale lock files?
> I've been having them for a few weeks now, they need to go away!
>
> root@curly /root# portupgrade -a
> ** Stale lock file was found. Removed.
> ** Stale lock file was found. Removed.
> [...]
>
> root@curly /root# portversion -c
> ** Stale lock file was found. Removed.
These are related to a (harmless) twitch in a recent version of
ruby. Updating to the latest version fixed it for me.
Robert Huff
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
On Jun 27, 2009, at 10:42 AM, Robert Huff wrote:
>
> Charles Howse writes:
>
>> What are stale lock files?
>> I've been having them for a few weeks now, they need to go away!
>>
>> root@curly /root# portupgrade -a
>> ** Stale lock file was found. Removed.
>> ** Stale lock file was found. Removed.
>> [...]
>>
>> root@curly /root# portversion -c
>> ** Stale lock file was found. Removed.
>
> These are related to a (harmless) twitch in a recent version of
> ruby. Updating to the latest version fixed it for me.
Thanks Robert and Polytropon,
Running 'portversion -c' after 'portupgrade -a' no longer shows any
stale lock files.
Just wondering...is there any utility to find and remove these things?
Maybe a reboot?
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
Charles Howse writes:
> >> ** Stale lock file was found. Removed.
> >
> > These are related to a (harmless) twitch in a recent version of
> > ruby. Updating to the latest version fixed it for me.
>
> Running 'portversion -c' after 'portupgrade -a' no longer shows
> any stale lock files.
> Just wondering...is there any utility to find and remove these
> things? Maybe a reboot?
A successful run _after_ the aforementioned ruby upgrade should
remove all the laggards.
Robert Huff
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
Related Threads
- Patch, objc - maintenance, make Obj{C,C++} LTO-friendly. - gcc
- css - “text-rendering†property - web
- update - rpm2cpio 1.3 - openbsd
- osol-discuss - Oracle Solaris: General FAQs: seems from july - opensolaris
- Hendrix - Keeps Crashing - firefox
- Hendrix - new update sucks - firefox
- PATCH: Require OSXSAVE for AVX run-time tests - gcc
- Hendrix - problem using google search - firefox
- Re: system hangs on; Probing devices, please wait (this can take a while)... - freebsd
- Master/Slave and non-persistence message - activemq
- Bug 23779 - New: Graphviz msiexec installer fails with Installation Incomplete: The installer was interupted before Graphviz co - wine
- css3-values - proposal for handling division and units in calc() ACTION-205 - - web