On 14/10/2013 06:37, Beeblebrox wrote:
Hi,
I Inadvertently posted the gnome-keyring bit. That's almost standard error
message on FreeBSD-Gnome. The relevant bit for the error is in fact:
slim: gkr-pam: no password is available for user
However, the user cannot login on a tty without providing a
I have two strange errors but I am not sure whether they are related.
ERROR-1: Slim allows login without checking for password. /var/log/auth.log
shows:
Oct 13 11:44:57: slim: gkr-pam: no password is available for user
Oct 13 11:44:57: gnome-keyring-daemon[1225]: couldn't allocate secure memory
On 13/10/2013 18:08, Beeblebrox wrote:
I have two strange errors but I am not sure whether they are related.
ERROR-1: Slim allows login without checking for password. /var/log/auth.log
shows:
Oct 13 11:44:57: slim: gkr-pam: no password is available for user
Oct 13 11:44:57: gnome-keyring-daemon
:
http://freebsd.1045724.n5.nabble.com/Authorisation-Errors-on-9-2-tp5851543p5851636.html
Sent from the freebsd-questions mailing list archive at Nabble.com.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
of compile errors:
/../gcc-4.6.3/libgfortran/../gcc -I../.././../gcc-4.6.3/libgfortran/../gcc/confi
g -I../.././../gcc-4.6.3/libgfortran/../libquadmath -I../.././gcc -D_GNU_SOURCE
-std=gnu99 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition
-Wextra -Wwrite-strings -fcx-fortran-rules
of this
community edition (GPLv2).
seems to be the source of these errors which are biting me too.
It would be nice for some clearer documentation on why distinfo was
changed, what the real issue is, and what we can do to build this
correctly. Naively speaking, the version available for download off
- to
match the distinfo file, but they no longer do. This cryptic comment:
Distfile rerolled to make it clearer the license of this
community edition (GPLv2).
seems to be the source of these errors which are biting me too.
It would be nice for some clearer documentation on why distinfo
Hi all,
There is an error when poudriere tries to build mysql55-client:
=== License GPLv2 accepted by the user
=== Fetching all distfiles required by mysql-client-5.5.32 for building
= SHA256 Checksum mismatch for mysql-5.5.32.tar.gz.
=== Refetch for 1 more times files: mysql-5.5.32.tar.gz
Hi,
There is an error when poudriere tries to build mysql55-client:
st in /distfiles/.
= Attempting to fetch
ftp://ftp.gwdg.de/pub/misc/mysql/Downloads/MySQL-5.5/mysql-5.5.32.tar.gz
fetch: mysql-5.5.32.tar.gz: local file (24625029 bytes) is longer than
remote file (24589274 bytes)
I'd say
On Thu, Jun 27, 2013 at 8:05 AM, Olivier Nicole
olivier.nic...@cs.ait.ac.th wrote:
Hi,
There is an error when poudriere tries to build mysql55-client:
st in /distfiles/.
= Attempting to fetch
ftp://ftp.gwdg.de/pub/misc/mysql/Downloads/MySQL-5.5/mysql-5.5.32.tar.gz
fetch:
On Thu, 27 Jun 2013 07:55-, C. L. Martinez wrote:
Hi all,
There is an error when poudriere tries to build mysql55-client:
=== License GPLv2 accepted by the user
=== Fetching all distfiles required by mysql-client-5.5.32 for building
= SHA256 Checksum mismatch for
On Thu, Jun 27, 2013 at 9:21 AM, Trond Endrestøl
trond.endres...@fagskolen.gjovik.no wrote:
On Thu, 27 Jun 2013 07:55-, C. L. Martinez wrote:
Hi all,
There is an error when poudriere tries to build mysql55-client:
=== License GPLv2 accepted by the user
=== Fetching all distfiles
I am working on a FBSD 9.1-STABLE mail machine that's been working
fine. After upgrading to MailScanner 4.84.5_3, we are now
suddenly seeing like this:
Clamd::ERROR:: UNKNOWN CLAMD RETURN ./lstat() failed: Permission denied.
ERROR :: /var/spool/MailScanner/incoming/68340
Any ideas what
Hi Tim,
Double check what user clamd is run as, and what permissions your mail
spool have. Somewhere along the line your mail spool locked out clamd
The lstat system call's man page says
`execute (search) permission is required on all of the
directories in path that lead to the file.`
Also,
On Thu, 16 May 2013 18:30:05, C. L. Martinez wrote:
CLM === Building for vortex-2.9.0.59
CLM cd /wrkdirs/usr/ports/net/vortex/work/vortex-2.9.0 cc -c vortex.c
CLM -I/usr/local/include
CLM cd /wrkdirs/usr/ports/net/vortex/work/vortex-2.9.0 cc -o vortex
CLM vortex.o -L/usr/local/lib
Hi all,
I am trying to build vortex port using poudriere in a FreeBSD 9.1
amd64 host, but it fails:
===
=== Returning to build of vortex-2.9.0.59
=== vortex-2.9.0.59 depends on file: /usr/local/bin/libnet11-config
-
This is not very helpful, but you can try Pause, Scroll Lock, high FPS
filming and pause or taking pictures with short exposure.
On Mon, Feb 25, 2013 at 6:20 AM, Martin Alejandro Paredes Sanchez
mapsw...@prodigy.net.mx wrote:
On Sunday 24 February 2013 14:33:06 Ronald F. Guilmette wrote:
I
barely make out that they seem to relate to ada2...
well, anyway, one or another of the hard drives.
I do not know the proper way to rectify whatever is causing these flaky
errors. I use the term flaky because, as I have said, this boot-time
problem only seems to occur maybe about 50% of the time
.
I do not know the proper way to rectify whatever is causing these flaky
errors. I use the term flaky because, as I have said, this boot-time
problem only seems to occur maybe about 50% of the time, and the rest
of the time when I boot up there is no problem whatsoever.
Because I am able to boot
On Sunday 24 February 2013 14:33:06 Ronald F. Guilmette wrote:
I have a somewhat eclectic system, currently running (or at any rate,
trying to run) 9.1-RELEASE. The system in question contains three
drives, to wit:
WDC WD1002FAEX-00Z3A0 05.01D05 ATA-8 SATA 3.x device
ST3500320AS SD1A
Hi all.
I have uname -rms
FreeBSD 10.0-CURRENT amd64
I use to build system for architecture MIPS the instructions on the wiki
http://wiki.freebsd.org/FreeBSD/mips
I use next script build.sh http://privatepaste.com/339d25c604
but the compilation fails http://privatepaste.com/106d4015d0
then I
That's odd. I don't build like that though, I build with my build
scripts at http://code.google.com/p/freebsd-wifi-build/
Maybe see what I do in build_freebsd ?
Adrian
On 7 November 2012 04:37, Ivan Klymenko fi...@ukr.net wrote:
Hi all.
I have uname -rms
FreeBSD 10.0-CURRENT amd64
I
I'd loose the -D flags and try again. The instructions there are very odd.
Warner
On Nov 7, 2012, at 5:37 AM, Ivan Klymenko wrote:
Hi all.
I have uname -rms
FreeBSD 10.0-CURRENT amd64
I use to build system for architecture MIPS the instructions on the wiki
Thanks, I'll try to figure out how to use it :)
В Wed, 7 Nov 2012 08:46:56 -0800
Adrian Chadd adr...@freebsd.org пишет:
That's odd. I don't build like that though, I build with my build
scripts at http://code.google.com/p/freebsd-wifi-build/
Maybe see what I do in build_freebsd ?
Hi,
unfortunately I have the same problem. A lot of fetch and checksum errors. I
have set RESOLV_CONF=/etc/resolv.conf in /usr/local/etc/poudriere.conf,
resolv.conf is copied to the poudriere jail and manual fetching of the ports is
working.
On every run of poudriere bulk different ports
On 11/2/2012 11:52 AM, Wolfgang Riegler wrote:
Hi,
unfortunately I have the same problem. A lot of fetch and checksum errors. I
have set RESOLV_CONF=/etc/resolv.conf in /usr/local/etc/poudriere.conf,
resolv.conf is copied to the poudriere jail and manual fetching of the ports
is working
On Fri, 19 Oct 2012 22:29:51 +0200
Patrick Lamaiziere patf...@davenulle.org wrote:
Le Sun, 14 Oct 2012 03:57:20 +0200,
Christopher J. Ruwe c...@cruwe.de a écrit :
Hello,
for some time I have noticed that poudriere bulk build amass fetch
errors, i.e., the corresponding distfile(s
Le Sun, 14 Oct 2012 03:57:20 +0200,
Christopher J. Ruwe c...@cruwe.de a écrit :
Hello,
for some time I have noticed that poudriere bulk build amass fetch
errors, i.e., the corresponding distfile(s) cannot be fetched by the
build jail and I have to fetch these manually.
Does anybody know
Hello,
for some time I have noticed that poudriere bulk build amass fetch
errors, i.e., the corresponding distfile(s) cannot be fetched by the
build jail and I have to fetch these manually.
Does anybody know a fix to this unnerving condition?
Cheers,
--
Christopher J. Ruwe
TZ: GMT + 2h
to see if it makes a difference.
Can limiting write speed avoid these errors?
That depends on both the drive and the media.
It's also possible that it makes matters worse, though.
It's a myth that reducing speed guarantees better results.
And what
limiting write speed avoid these errors?
That depends on both the drive and the media.
It's also possible that it makes matters worse, though.
It's a myth that reducing speed guarantees better results.
And what ways are there to
detect the fastest
I'm using growisofs to write DVDs of backup files. Some combinations of
older drives and newer media give :-( unable to PERFORM OPC:
Input/output error.
Can limiting write speed avoid these errors? And what ways are there to
detect the fastest speed supported by both drive and media
that came out of a barebones PC that I replaced with a couple
smaller drives in a stripe to gain performance. I use the drives in an
external SATA dock, using geom eli encryption, the western digital
drives give me no problems, but the seagate drive gives me a lot of the
following errors under
Just curious, I am sure the likely issue is a bad disk, but I thought there
actually not that likely.
i had such problems, occuring randomly on many drives, and all problems
disappeared after changing computer, with the same disk.
BTW i would recommend you to turn on AHCI driver
ad4:
performance. I use the drives in an external
SATA dock, using geom eli encryption, the western digital drives give me
no problems, but the seagate drive gives me a lot of the following errors
under load.
ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=817755328
ad4: WARNING - WRITE_DMA48 UDMA
dweimer dweimer at dweimer.net writes:
...
ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=817755328
ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request)
LBA=837397120
...
There is a story about it:
On 2012-07-24 12:50, Wojciech Puchar wrote:
Just curious, I am sure the likely issue is a bad disk, but I
thought there
actually not that likely.
i had such problems, occurring randomly on many drives, and all
problems disappeared after changing computer, with the same disk.
BTW i would
smaller
drives in a stripe to gain performance. I use the drives in an
external
SATA dock, using geom eli encryption, the western digital drives
give me
no problems, but the seagate drive gives me a lot of the following
errors
under load.
ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA
On 2012-07-24 13:37, jb wrote:
dweimer dweimer at dweimer.net writes:
...
ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=817755328
ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request)
LBA=837397120
...
There is a story about it:
dweimer dweimer at dweimer.net writes:
...
188 Command_Timeout -O--CK 100 098 000-
21475164202
...
I can not find it for Seagate;
http://sourceforge.net/apps/trac/smartmontools/wiki/AttributesSeagate
but for Western-Digital:
, most of the numbers don't look really bad, but I'd cast a leery eye
towards the way these three correlate. Read errors from bad spots in the
magnetic media are one thing, but notice how the drive is recovering data
with built-in ECC routines. Then notice that the seek error rate is moving
along
a lot of the following errors under load.
ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=817755328
ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=837397120
ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=879786112
ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying
no problems, but the seagate drive
gives me a lot of the following errors under load.
ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=817755328
ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request)
LBA=837397120
ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=879786112
ad4
,
but the seagate drive gives me a lot of the following errors under load.
ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=817755328
ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=837397120
ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=879786112
ad4: WARNING
, the western digital drives give me no
problems, but the seagate drive gives me a lot of the following errors
under load.
ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left)
LBA=817755328
ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying
request) LBA=837397120
ad4: TIMEOUT - WRITE_DMA48 retrying
The big report that google published made it clear that even a single scan
error in the SMART data of a disk drive is a good predictor of eventual
failure...
However, when I run smartctl:
# smartctl -a /dev/da0 | grep -i pre-fail
1 Raw_Read_Error_Rate 0x000b 100 100 016Pre-fail
On 09/07/2012 16:12, Jason Usher wrote:
What is a scan error, and which metric should I tell smartctl to check ?
I think they mean a SMART scan, as in a self-test -
http://www.twopenguins.it/2011/12/test-an-hard-disk-with-smartctl/ has
details of how to run it.
--
Bruce Cran
Hi,
On Fri, 04 May 2012 14:12:17 +0200
Hartmann, O. ohart...@zedat.fu-berlin.de wrote:
HO I found myself incapable of rebuilding/updating editors/libreoffice
HO on ALL FreeBSD 9-STABLE and FreeBSD 10-CURRENT (amd64) platforms
HO with the very same error message as shown below.
I ran into the
2012-05-31 19:35, Jens Jahnke skrev:
Hi,
On Fri, 04 May 2012 14:12:17 +0200
Hartmann, O.ohart...@zedat.fu-berlin.de wrote:
HO I found myself incapable of rebuilding/updating editors/libreoffice
HO on ALL FreeBSD 9-STABLE and FreeBSD 10-CURRENT (amd64) platforms
HO with the very same
/64 bit incompatibilities (some
weird errors occur, not further investigated).
It seems impossible to rebuild even a former installed version of
libreoffice.
Resources are no problem, I build Libreoffice with DISABLE_MAKE_JOBS
and in one case the box has 32GB of RAM - and is free of other duties
Hartmann, O. ohart...@zedat.fu-berlin.de wrote:
Cc:
Subject: editors/libreoffice:internal build errors: ERROR: error 65280
I found myself incapable of rebuilding/updating editors/libreoffice on
ALL FreeBSD 9-STABLE and FreeBSD 10-CURRENT (amd64) platforms with the
very same error message
On 05/04/12 19:01, Robert Bonomi wrote:
Hartmann, O. ohart...@zedat.fu-berlin.de wrote:
Cc:
Subject: editors/libreoffice:internal build errors: ERROR: error 65280
I found myself incapable of rebuilding/updating editors/libreoffice on
ALL FreeBSD 9-STABLE and FreeBSD 10-CURRENT (amd64
Just downloaded phpmyadmin for 9.0 system.
The port files seem to be named wrong.
Makefile,v distinfo,v pkg-descr,v pkg-plist-chunk,v
make install command issues error message Don't know how to make install.
I see on the web ports system that this port was just updated 5 days
ago. Looks
On Tue, Apr 03, 2012 at 03:14:39PM -0400, Fbsd8 thus spake:
Just downloaded phpmyadmin for 9.0 system.
The port files seem to be named wrong.
Makefile,v distinfo,v pkg-descr,v pkg-plist-chunk,v
make install command issues error message Don't know how to make install.
I see on the web ports
On Tue, 03 Apr 2012 15:14:39 -0400
Fbsd8 fb...@a1poweruser.com wrote:
Just downloaded phpmyadmin for 9.0 system.
The port files seem to be named wrong.
Makefile,v distinfo,v pkg-descr,v pkg-plist-chunk,v
make install command issues error message Don't know how to make
install.
I see
and get a slew of errors. Here we go..
(da3:mpt0:0:6:1): Logical unit not accessible, target port in standby state
(da3:mpt0:0:6:1): Retrying Command (per Sense Data)
(da3:mpt0:0:6:1): READ(10). CDB: 28 0 0 0 0 0 0 0 1 0
(da3:mpt0:0:6:1): CAM Status: SCSI Status Error
(da3:mpt0:0:6:1): SCSI Status
it and I get a
50% return rate. So I log in to the management blade and start a virtual KVM
sessions to get into the blade. Once I'm into the basehost blade, I cat
dmesg.today and get a slew of errors. Here we go..
(da3:mpt0:0:6:1): Logical unit not accessible, target port in standby state
On 12/22/11 15:11, Da Rock wrote:
Just something for the kids, but I'm wondering how to get this to work?
I've installed from ports, but when I run it from the cli to test it I
get an error:
Traceback (most recent call last):
File /usr/local/bin/pysycache.py, line 442, in module
if
On Thu, 22 Dec 2011 23:13:53 +1000, Da Rock wrote:
%env LANG=en_EN.ISO8859-1 pysycache.py
^^
Isn't that supposed to be en_US or en_GB?
I'm not sure if there's also en_AU... :-)
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
On 12/22/11 23:20, Polytropon wrote:
On Thu, 22 Dec 2011 23:13:53 +1000, Da Rock wrote:
%env LANG=en_EN.ISO8859-1 pysycache.py
^^
Isn't that supposed to be en_US or en_GB?
I'm not sure if there's also en_AU... :-)
The one variation I didn't try I had tried en_US and en_AU,
On Thu, 22 Dec 2011 23:57:28 +1000, Da Rock wrote:
On 12/22/11 23:20, Polytropon wrote:
On Thu, 22 Dec 2011 23:13:53 +1000, Da Rock wrote:
%env LANG=en_EN.ISO8859-1 pysycache.py
^^
Isn't that supposed to be en_US or en_GB?
I'm not sure if there's also en_AU... :-)
The
Just something for the kids, but I'm wondering how to get this to work?
I've installed from ports, but when I run it from the cli to test it I
get an error:
Traceback (most recent call last):
File /usr/local/bin/pysycache.py, line 442, in module
if __name__ == '__main__':
I am running 9.0 BETA2 and I see these errors in /var/log/messages:
Sep 16 18:07:51 store2 kernel: GEOM: da1: corrupt or invalid GPT detected.
Sep 16 18:07:51 store2 kernel: GEOM: da1: GPT rejected -- may not be
recoverable.
Sep 16 19:13:25 store2 kernel: lock order reversal:
Sep 16 19:13:25
Op 18-09-11 18:35, free...@top-consulting.net schreef:
I am running 9.0 BETA2 and I see these errors in /var/log/messages:
Sep 16 18:07:51 store2 kernel: GEOM: da1: corrupt or invalid GPT
detected.
Sep 16 18:07:51 store2 kernel: GEOM: da1: GPT rejected -- may not be
recoverable.
Sep 16 19
/freebsd-current/attachments/20091101/4084
8244/ifmcstat.obj
Regards,
// Mem
- On 1st of January 2011 Manolis Kiagias wrote: -
Subject: Re: make buildworld errors
From: Manolis Kiagias
Date: Sat, 01 Jan 2011 00:35:37 -0800
On 01/01/2011 9:54 ?.?., Mike wrote:
Trying to buildworld
After following the handbook Chapter 24 to upgrade from 8.1 to 8.2, I am
getting kernel errors for various postfix commands...
May 9 08:54:13 mx3 kernel: pid 57056 (trivial-rewrite), uid 125: exited
on signal 11
May 9 08:56:46 mx3 kernel: pid 57086 (smtpd), uid 125: exited on signal 11
I
On Mon, 09 May 2011 08:54:29 -0400
Robert Fitzpatrick rob...@webtent.org articulated:
After following the handbook Chapter 24 to upgrade from 8.1 to 8.2, I
am getting kernel errors for various postfix commands...
{snip}
I would strongly suggest that you post this on the Postfix forum. Be
sure
Robert Fitzpatrick rob...@webtent.org writes:
After following the handbook Chapter 24 to upgrade from 8.1 to 8.2, I
am getting kernel errors for various postfix commands...
May 9 08:54:13 mx3 kernel: pid 57056 (trivial-rewrite), uid 125:
exited on signal 11
May 9 08:56:46 mx3 kernel: pid
I updated the ports after the reboot and did a 'portupgrade -af'
after the kernel update, restart, etc. I had no issues performing
the upgrade according to the handbook and the System State
Comparison seems OK...
Did you do the whole
mergemaster -p
make buildworld
make buildkernel
make
On 5/9/2011 12:33 PM, Reko Turja wrote:
I updated the ports after the reboot and did a 'portupgrade -af'
after the kernel update, restart, etc. I had no issues performing the
upgrade according to the handbook and the System State Comparison
seems OK...
Did you do the whole
mergemaster -p
mx3# mergemaster -p
*** Creating the temporary root environment in /var/tmp/temproot
*** /var/tmp/temproot ready for use
*** Creating and populating directory structure in
/var/tmp/temproot
cp: /usr/src/etc/master.passwd: No such file or directory
*** FATAL ERROR: Cannot copy files to
Some time ago, emacs started doing this on startup under X:
(emacs:65141): GLib-WARNING **: In call to g_spawn_sync(), exit status
of a child process was requested but SIGCHLD action was set to SIG_IGN
and ECHILD was received by waitpid(), so exit status can't be
returned. This is a bug in the
bind. I've tried to fix these errors:
nothing. Does anybody onlist know how I can build in the
/contrib/bind/*/*? What flags to set in the /usr/src/Makefile? Or::
howt o fix this mess below?
Jan 23 01:07:14 ethic named[3229]: starting BIND 9.7.2-P3 -c
/var/named/etc/namedb/named.conf
Jan 23
/ifmcstat/ifmcstat.c
cc1: warnings being treated as errors
/usr/src/usr.bin/ifmcstat/ifmcstat.c:170: warning: 'in6_ifinfo' used
but never defined
*** Error code 1
Stop in /usr/src/usr.sbin/ifmcstat.
*** Error code 1
#uname -a
FreeBSD frogger 8.1-RELEASE-p1 FreeBSD 8.1-RELEASE-p1 #0: Sat Nov 27
02:47:28
On 01/01/2011 9:54 ?.?., Mike wrote:
Trying to buildworld but it keeps failing. I finally deleted /usr/src
and recopyed from a cd then cvsup using standard-supfile. Tried
limiting how much ram freebsd uses and only using one stick of ram.
All attempts have failed at the same place. Would
I have a lot of these errors in /var/log/messages
gnome-keyring-daemon[2169]: couldn't set environment variable in
session: The name org.gnome.SessionManager was not provided by any
.service files
I don't use gnome-keyring but some of the ports I use has pulled it in.
Uninstalling
Hi,
It looks like mx2.freebsd.org is blacklisted by Sorbs.net:
Original Message Transcript of session follows.
In: EHLO mx2.freebsd.org
Out: 250-PIPELINING
Out: 250-SIZE 2560
Out: 250-ETRN
Out: 250-ENHANCEDSTATUSCODES
Out: 250-8BITMIME
Out: 250 DSN
In: MAIL
From owner-freebsd-questi...@freebsd.org Fri Sep 10 17:51:18 2010
From: cronfy cro...@gmail.com
Date: Sat, 11 Sep 2010 02:27:46 +0400
To: freebsd-questions freebsd-questions@freebsd.org
Subject: fsck reports errors on clean filesystem (mounted rw)
Hello.
I ran fsck on my filesystems
On Sun, 12 Sep 2010 16:16:53 -0500 (CDT)
Robert Bonomi bon...@mail.r-bonomi.com wrote:
There are exactly _four_ possible causes of file-system
inconsistencies. 1) You can have an unexpected loss of power, where
the CPU stops working before it as time to write the above-mentioned
Hello.
I ran fsck on my filesystems while system was running (partitons were
mounted rw with moderate FS usage). fsck reported there were errors
(INCORRECT BLOCK COUNT and others). I decided to reboot to single mode
and check all filesystems. But in single mode fsck did not find any
errors.
1
On Sep 10, 2010, at 3:27 PM, cronfy wrote:
1. Can I be sure my filesystem is consistent?
Reasonably.
2. If fsck reports nonexistent errors (and probably will try to fix
them if asked), isn't it even danger to run fsck on running system?
Running fsck in foreground mode on a mounted filesystem
Hi,
I am trying to get the DVD burner running on 8.1
The machine: 8.1-STABLE FreeBSD 8.1-STABLE #3: Sat Jul 24 20:56:05 SGT 2010
I have atapicam enabled. I lock HAL. Still, it seems I am missing something or
there is a problem with my hardware.
The command:
hal-lock --interface
Is anyone getting these errors when logging in to Squirrel Mail?
Warning: strtotime() [function.strtotime]: It is not safe to rely on
the system's timezone settings. You are *required* to use the
date.timezone setting or the date_default_timezone_set() function. In
case you used any of those
On Sat, Jul 10, 2010 at 9:01 PM, Chris Maness ch...@chrismaness.com wrote:
Is anyone getting these errors when logging in to Squirrel Mail?
Warning: strtotime() [function.strtotime]: It is not safe to rely on
the system's timezone settings. You are *required* to use the
date.timezone setting
On Sat, Jul 10, 2010 at 8:43 AM, Amitabh Kant amitabhk...@gmail.com wrote:
On Sat, Jul 10, 2010 at 9:01 PM, Chris Maness ch...@chrismaness.com wrote:
Is anyone getting these errors when logging in to Squirrel Mail?
Warning: strtotime() [function.strtotime]: It is not safe to rely
Am 05.07.2010 21:39, schrieb Polytropon:
On Mon, 05 Jul 2010 16:09:23 +0200, Christoph Kukuliesk...@kukulies.org
wrote:
I tried PHKs' recoverdisk with recoverdisk -b 1024000 /dev/ad2 ad2.dmp
and it went off quite promising just few dma read timeouts and when I
was at 7% of recovery
it
Am 06.01.2010 02:30, schrieb Polytropon:
On Tue, 05 Jan 2010 15:31:46 +0100, Christoph Kukuliesk...@kukulies.org
wrote:
It copies a disk sector by sector to a file (kind of dd), but ignores
errors, it just skips sectors it couldn't read (after a couple
of retries). The result
On Mon, 05 Jul 2010 16:09:23 +0200, Christoph Kukulies k...@kukulies.org
wrote:
Some student lost some important data due to disk failure.
He will restore it easily from backup. :-)
I tried PHKs' recoverdisk with recoverdisk -b 1024000 /dev/ad2 ad2.dmp
and it went off quite promising
errors
come up.
i have heard that the ports are more stable than portage but with
portage i
didn't have so many errors (actually i can't recall a time when
portage
died)
am i doing sth wrong or ports comes up with many errors??
P.S.: 1 week not i haven't manage to install a graphical
On 06/06/2010 1:39 π.μ., Giorgos Tsiapaliokas wrote:
hello,
i am coming from the linux world i was a gentoo user and i have install on
my second machine FBSD,i have made many formats but every time i try to
install a graphical enviroment (such as xfce,kde) many many errors come up.
i have
On 06/06/2010 1:11 ?.?., Giorgos Tsiapaliokas wrote:
i have FBSD 8.0 i have install the base system plus the bash shell
from the CD.after the installiation of the system i install ports with
portsnap and i update them with portmaster,no error came up,but now i
receive errors from xfce4
,no error came up,but now i
receive errors from xfce4.
@*Alejandro Imass*
*
*
what do u mean when u say?
Tip: in FBSD the word stable has a completely
different meaning than in the LInux world ;-)
(adding the list to the recipients)
Don't install bash from CD. Bash will also
hello,
i am trying to compile xorg and kde 4 but i receive these 2 errors.
i have updated the ports.
the kde error
=== kde4-4.4.4_1 depends on file: /usr/local/kde4/bin/kdebugdialog - not
found
===Verifying install for /usr/local/kde4/bin/kdebugdialog in
/usr/ports/x11/kdebase4-runtime
On Sunday 06 of June 2010 19:38:29 Giorgos Tsiapaliokas wrote:
hello,
i am trying to compile xorg and kde 4 but i receive these 2 errors.
i have updated the ports.
the kde error
=== kde4-4.4.4_1 depends on file: /usr/local/kde4/bin/kdebugdialog - not
found
===Verifying install
hello,
i am trying to compile xorg and kde 4 but i receive these 2 errors.
i have updated the ports.
The errors are all coming from a failure to install the dependency
textproc/iso8879. What is the output of 'make -C
/usr/ports/textproc/iso8879 checksum' ? If it fails, try deleting
On 6/6/10, b. f. bf1...@googlemail.com wrote:
...
your other port builds. textproc/iso8879 may be modified soon,
because unqualified use of 'unzip' in the install target seems to be
causing confusion between the new base system unzip and
archivers/unzip, which may have consequences for the
errors come up.
i have heard that the ports are more stable than portage but with portage i
didn't have so many errors (actually i can't recall a time when portage
died)
am i doing sth wrong or ports comes up with many errors??
Need to specify FBSD version. I had many problems
Hi! I'm using the auto-mount daemon to access another server via NFS, and I
keep getting error messages in `/var/log/messages`:
May 27 01:03:26 hedwig amd[9851]: mountd rpc failed: RPC: Can't decode
result
May 27 01:03:26 hedwig last message repeated 4 times
My searches so far
Richard Morse remo...@partners.org writes:
Hi! I'm using the auto-mount daemon to access another server via NFS, and I
keep getting error messages in `/var/log/messages`:
May 27 01:03:26 hedwig amd[9851]: mountd rpc failed: RPC: Can't decode
result
May 27 01:03:26 hedwig last
Hi all:
I am compiling xscreensaver-kde and it stooped with following errors:
Package tocloft Note: The document has chapter divisions.
) (/usr/local/share/texmf-dist/tex/latex/hyperref/hyperref.sty
(/usr/local/share/texmf-dist
1 - 100 of 1270 matches
Mail list logo
