it be safe to put elogind in the default runlevel?� That
would solve the problem of me forgetting to restart it after upgrades.
Or would some other service in the boot runlevel start it as a
dependency anyway??
When I get to a point where I can logout and back in, I'll test
restarting elogind
it to go to a separate file TOO, but not ONLY.
Here's the entire syslog-ng.conf and the service file for dhcpd.
Hopefully you guys can figure something out I missed:
(dhcpd4.service)
[Unit]
Description=DHCPv4 Server Daemon
Documentation=man:dhcpd(8) man:dhcpd.conf(5)
After=network.target
After
complain if it went faster. I think it is about as
> >> fast as it is going to get tho.
> >
> > And that may be contributing to the CPU usage. Slowing down the flow may
> > make the comouter more usable, and you're never going to copy 26TB
> > quickly, especially
_ruby30 ? dev-lang/ruby:3.0)
dev-ruby/singleton-0.1.1 (ruby_targets_ruby30 ? dev-lang/ruby:3.0)
dev-ruby/stringio-3.0.8 (ruby_targets_ruby30 ? dev-lang/ruby:3.0)
dev-ruby/test-unit-3.6.1 (ruby_targets_ruby30 ? dev-lang/ruby:3.0)
dev-ruby/time-0.2.2 (ruby_targets_ruby30 ? dev-lang/ruby:3.0)
test xinerama
+xklavier ELIBC=glibc}
Installed versions: 3.6.2(22:49:57 28.01.2013)(fallback
gnome-shell introspection ipv6 systemd tcpd xinerama
[I] gnome-base/gnome-session
Available versions: 2.32.1-r3 (~)3.4.2.1 (~)3.6.2 (~)3.6.2-r1
**[1] {debug doc gconf ipv6 systemd ELIBC
On Sat, 26 May 2012 23:22:22 -0700
Grant emailgr...@gmail.com wrote:
Extensive testing, on the other hand, is something a team should do.
Sure, the lone programmer can write you some unit tests and conduct
a system test, but testing itself is a profession of its own and
should be done
, and now again my LVM test system works
perfectly with the latest dracut version.
I'm an idiot; I didn't saw the documentation about hostonly_cmdline;
BTW Jc, you used host_cmdline, I think the former is the correct one.
So, to resume: there is no bug, is just that before hostonly_cmdline
was yes
]
* Found these USE flags for sys-apps/systemd-218-r3:
U I
+ + abi_x86_32 : 32-bit (x86) libraries
+ + acl: Add support for Access Control Lists
- - audit : Enable support for sys-process/audit
- - cryptsetup : Ena
ev/sdb
> >>
> >> Device Identification VPD page:
> >> Addressed logical unit:
> >> designator type: NAA, code set: Binary
> >>
> >> 0x600605b00d0ce810217ccffe19f851e8
> >
> > Yes, this one is different.
> >
>
dumpio
-http2 -ident -imagemap -lbmethod_bybusyness -lbmethod_byrequests
-lbmethod_bytraffic -lbmethod_heartbeat -log_forensic -macro -proxy
-proxy_ajp -proxy_balancer -proxy_connect -proxy_fcgi -proxy_ftp
-proxy_html -proxy_http -proxy_scgi -proxy_wstunnel -ratelimit -remoteip
-reqtimeout -slotmem
FLUSH_CACHE
*FLUSH_CACHE_EXT
*SMART error logging
*SMART self-test
*General Purpose Logging feature set
*Segmented DOWNLOAD_MICROCODE
*Gen1 signaling speed (1.5Gb/s)
*Gen2 signaling speed (3.0Gb/s
*SMART error logging
*SMART self-test
*General Purpose Logging feature set
*Segmented DOWNLOAD_MICROCODE
*Gen1 signaling speed (1.5Gb/s)
*Gen2 signaling speed (3.0Gb/s)
*Host-initiated interface
.
Bugs get reported, bugs get fixes. Life goes on.
You didn't answered this, did you?
Bugs are different.
Bugs are bugs, period. And they get reported and fixed.
Bugs in the critical system components are
critical to the whole system.
Yeah, that's why we have unit testing
usr/bin/gacutil
> checking for al... /usr/bin/al
> checking for x86_64-pc-linux-gnu-pkg-config... (cached) /usr/bin/pkg-config
> checking pkg-config is at least version 0.9.0... yes
> checking for GTK_SHARP_20... yes
> configure: creating ./config.status
> config.status: creating .
/Makefile
config.status: creating ./Mono.Addins.MSBuild/Makefile
config.status: creating ./mautil/Makefile
config.status: creating ./mautil/mautil
config.status: creating ./docs/Makefile
config.status: creating ./Test/HelloWorldExtension/Makefile
config.status: creating ./Test/FileContentExtension/Make
QA processes, test/stage VMs, unit tests, and being
able to enforce those processes. Gentoo allows enormous flexibility and
being able to have things like glibc-2.9 immediately while RHEL4 shipped
with 2.3 and RHEL5 with 2.5 means you can take advantage of incremental
fixes in NPTL
hole. Now ain't that something? Dale is going to the shop and
getting his mini sledge
Dale
I was about to suggest you search http://www.apc.com/support/answers.cfm for a
possible meaning to status -121 from APC. Assuming it's an APC unit. I can't
search for you cause they demand cookies
:
GRUB_CMDLINE_LINUX=init=/usr/lib/systemd/systemd quiet nosplash
rd.lvm.lv=vg/vol1 rd.lvm.lv=vg/vol4 rd.lvm.lv=vg/vol3
rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12
I regenerated my GRUB2 config, and now again my LVM test system works
perfectly with the latest dracut version.
I'm an idiot; I didn't
:
GRUB_CMDLINE_LINUX=init=/usr/lib/systemd/systemd quiet nosplash
rd.lvm.lv=vg/vol1 rd.lvm.lv=vg/vol4 rd.lvm.lv=vg/vol3
rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12
I regenerated my GRUB2 config, and now again my LVM test system works
perfectly with the latest dracut version.
I'm an idiot; I
, and now again my LVM test system works
perfectly with the latest dracut version.
I'm an idiot; I didn't saw the documentation about hostonly_cmdline;
BTW Jc, you used host_cmdline, I think the former is the correct one.
So, to resume: there is no bug, is just that before hostonly_cmdline
t;> dev-lang/ruby:2.1
>> dev-ruby/net-telnet-0.1.1-r1 requires dev-lang/ruby:2.1
>> dev-ruby/power_assert-1.0.2 requires dev-lang/ruby:2.1
>> dev-ruby/racc-1.4.14 requires dev-lang/ruby:2.1
>> dev-ruby/rake-12.0.0 requires dev-lang/ruby:2.1
the USB2 ports to
it, making everything run at USB2 speeds.
With USB2, hubs are required to have a translation unit that speeds USB1
packets up to USB2 speeds. Even with these translators you can incur delays
waiting for slower USB1 devices to respond as they will take ~4x longer, and
then the buffered data
y
(ATA) disk that remained.
So, the problem is partially solved.
However, I still do not understand the exact reason for it to appear.
Most probably, both my SATA disks have connection problems as
Oli Schmidt suggested from the very beginning, and because they
both have it, it points to the mother
he server-site:
$ systemctl restart cups
This will also restart the Systemd socket unit "cups.socket" and
"cups.path".
Make sure, that CUPS is running on "192.168.1.80:631":
$ ss -tulpan | grep "631"
tcp LISTEN 0 5
g (5.14.1(5/5.14)@01/30/2020): SVG rendering library for
the Qt5 framework
[?] dev-qt/qttest (5.14.2(5/5.14)@05/15/2020 -> (~)5.14.1(5/5.14)^t):
Unit testing library for the Qt5 framework
[?] dev-qt/qtwayland (5.14.2(5/5.14)@05/15/2020 ->
(~)5.14.1-r1(5/5.14)^t): Wayland platform pl
Qt5 framework
[I] dev-qt/qtsvg (5.14.1(5/5.14)@01/30/2020): SVG rendering library
for the Qt5 framework
[?] dev-qt/qttest (5.14.2(5/5.14)@05/15/2020 -> (~)5.14.1(5/5.14)^t):
Unit testing library for the Qt5 framework
[?] dev-qt/qtwayland (5.14.2(5/5.14)@05/15/2020 ->
(~)5.14.1-r1(5/5.14)^t): Wa
your virtual disk3 but only a little, instead of
being around 150MB/sec it might run at 80.
you might also like to try a simple test of the following (yes lvs count
as block devices)
# hdparm -t /dev/sda
# hdparm -t /dev/sdb
# hdparm -t /dev/sdc
# hdparm -t /dev/vg01/winserver_disk0
# hdparm -t
self-test
*General Purpose Logging feature set
*64-bit World wide name
*WRITE_UNCORRECTABLE_EXT command
*Segmented DOWNLOAD_MICROCODE
*SATA-I signaling speed (1.5Gb/s)
*SATA-II signaling speed (3.0Gb/s)
*Native Command
nderstand and agree ;-)
>
> good :)
>
> > > > # /usr/bin/sg_vpd --page=di /dev/sdb
> > > >
> > > > Device Identification VPD page:
> > > > Addressed logical unit:
> > > > designator type: NAA, code set: Binary
Top posting because this is just an interim update - no new real info
yet.
I think part of my problem is that i don't have any real USB3 device to
test with. It might end up being reasonable for a USB2 device plugged
into a USB3 port to show up connected to a USB2 hub - but that hub
rrdtool swap syslog"
declare -x CPU_FLAGS_X86="aes mmx mmxext popcnt sse sse2 sse3 sse4_1 sse4_2
ssse3"
declare -x CTARGET_default="x86_64-pc-linux-gnu"
declare -x CXXFLAGS="-O2 -pipe"
declare -x DEFAULT_ABI="amd64"
declare -x DEFINED_PHASES=" compile
st month. That seems strange to me. Munin doesn't show any other
>>>>> data point increasing like this over the time period. Any ideas?
>>>>>
>>>>> - Grant
>>>>>
>>>>
>>>> weird - does it reset on an interface rest
einfo "Generating (BPY) Blender Python API docs ..."
"${BUILD_DIR}"/bin/blender --background --python
doc/python_api/sphinx_doc_gen.py -noaudio || die "sphinx failed."
cd "${CMAKE_USE_DIR}"/doc/python_api || die
, there is a catalyst target for smokescreen/tinderbox building. I'm
not sure of the quality but it is supposed to start from a clean image for
each rebuild, and simply use the binary packages previously built. I'd
assume it uses the ebuilds's test suite to verify post-install
correctness, (yes
the secp521r1 curve or about its security.
You can list all available curves by:
openssl ecparam -list_curves
With this setup apache and postfix works great. You can test my server
with this URL:
https://www.ssllabs.com/ssltest/analyze.html?d=nykyri.euhideResults=on
So these ciphers are supported
things down, but
they should not cause a USB3 hub to be identifed as USB2, just to work
at the lower speed. Am I wrong about this?
With USB2, hubs are required to have a translation unit that speeds
USB1
packets up to USB2 speeds. Even with these translators you can incur
delays
waiting for slower
to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM.
Using generic SCSI-3/mmc-2 DVD-R/DVD-RW/DVD-RAM driver (mmc_dvd).
Driver flags : NO-CD DVD MMC-3 SWABAUDIO BURNFREE
Supported modes: PACKET SAO LAYER_JUMP
cdrecord: Warning: The DMA speed test has been skipped.
book type: DVD-R, Version 2.0x (2.5)
disc size
that semaphore-issue.
After booting my desktop with it I quickly tested:
# lvcreate -n test -L1G VG03
Logical volume test created
#
fine!
Three times ok ...
But I still face the fact that the LVs weren't activated at boot time.
Manual vgchange -ay needed ... or that self-written
(SENSORS_MAX197) [N/m/?] (NEW) m
generic cpu cooling support (CPU_THERMAL) [N/y/?] (NEW)
Support for the SMSC ECE1099 series chips (MFD_SMSC) [N/y/?] (NEW)
Dialog Semiconductor DA9055 PMIC Support (MFD_DA9055) [N/y/?] (NEW)
Texas Instruments LP8788 Power Management Unit Driver (MFD_LP8788) [N/y
--
Real Softservice
Huateng Tower, Unit 1788
Jia 302 3rd area of Jinsong, Chao Yang
Tel: +86 (10) 8773 0650 ext 603
Mobile: 135 9950 2413
http://www.realss.com
app-office/lyx-1.5.4:
`-- app-office/lyx-1.5.4
`-- x11-libs/libXrandr-1.2.2
`-- x11-libs/libX11-1.1.3
`-- x11-libs/xtrans-1.0.4
ed to enable it on the host are
> > pretty trivial.
>
> Sorry Fernando, I just now saw this thread on an old thread. I think that
> 'sys-cluster/ceph' is where I'd like to test your spin on the gcc-5.
> Ceph has RDMA (RoCE) in the 0.94 branch (in portage). You are definately
> ah
postconf html_directory readme_directory, or go to
# http://www.postfix.org/.
#
# For best results, change no more than 2-3 parameters at a time,
# and test if Postfix still works after every change.
# SOFT BOUNCE
#
# The soft_bounce parameter provides a limited safety net for
# testing. When
jwt-1.7.1-r1
dev-python/pyopenssl-19.1.0
dev-python/PySocks-1.7.1
dev-python/pyyaml-5.3.1
dev-python/requests-2.22.0
dev-python/requests-oauthlib-0.7.0
dev-python/rsa-4.0
dev-python/setuptools-44.0.0
dev-python/simplejson-3.17.0
dev-python/six-1.14.0
dev-python/ssl-fetch-0.4
dev-python/termcolor-1.1.0-r
by/net-telnet:1 dev-ruby/power_assert:0 dev-ruby/racc:0
dev-ruby/rake:0 dev-ruby/rdoc:0 dev-ruby/rubygems:0 dev-ruby/test-unit:2
dev-util/automoc:0 dev-util/boost-build:0 dev-util/cmake:0
dev-util/cppunit:0 dev-util/ctags:0 dev-util/desktop-file-utils:0
dev-util/gdbus-codegen:0 dev-util/google-perftoo
101 - 144 of 144 matches
Mail list logo
