[CentOS] [OT] bash here documents

2013-06-24 Thread Steve
Suppose I have this C++ program: #include int main (int argc, char** argv) { while (1) { char cmd[80]; std::cin.getline(cmd, 80); std::cout << "response to " << cmd << std::endl; } } compiled by: c++ -o junk junk.cpp and I have this bash script: #!/bin/bash ./

Re: [CentOS] [OT] bash here documents

2013-06-24 Thread Tony Mountifield
In article <20130624135817.10QZO.129278.root@cdptpa-web19-z02>, Steve wrote: > Suppose I have this C++ program: > #include > int main (int argc, char** argv) > { > while (1) > { > char cmd[80]; > std::cin.getline(cmd, 80); > std::cout << "response to " << cmd << st

Re: [CentOS] [OT] bash here documents

2013-06-24 Thread m . roth
Steve wrote: > Suppose I have this C++ program: > #include > int main (int argc, char** argv) > { > while (1) > { > char cmd[80]; > std::cin.getline(cmd, 80); > std::cout << "response to " << cmd << std::endl; > } > } > > compiled by: c++ -o junk junk.cpp > > an

[CentOS] Best solution for TRIM on CentOS 5.x

2013-06-24 Thread Wade Hampton
I am planning on using solid state disks with my CentOS 5.x systems. Currently, I am using EXT3 for the file system. >From what I can find, CentOS 5.x does not support TRIM on solid state disks? Is this correct? Should I obtain and build the updated hdparm and use that to trim my drives (for ex

[CentOS] Korganizer Calendar Alarms stopped working

2013-06-24 Thread ken
For a long time--years-- I've been using Korganizer's Calendar. But lately-- since the last kernel upgrade, I believe-- the alarms don't work anymore. I set an appointment and (most of the time) schedule an alarm (one or more) for it, but the small windows containing the reminders don't pop u

Re: [CentOS] Best solution for TRIM on CentOS 5.x

2013-06-24 Thread Nux!
On 24.06.2013 16:42, Wade Hampton wrote: > > Any other suggestions on solid state drives (other than noatime > on mounts). Make sure your partitions are correctly aligned (recent parted should take care of it). -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ___

Re: [CentOS] Korganizer Calendar Alarms stopped working

2013-06-24 Thread Frank Cox
On Mon, 24 Jun 2013 12:17:12 -0400 ken wrote: > For a long time--years-- I've been using Korganizer's Calendar. But > lately-- since the last kernel upgrade, I believe-- the alarms don't > work anymore. Is korganizer calendar alarm the same thing as kalarm? kalarm works fine for me but I don

Re: [CentOS] [OT] bash here documents

2013-06-24 Thread Steve
Tony Mountifield wrote: > In article <20130624135817.10QZO.129278.root@cdptpa-web19-z02>, > Steve wrote: > > Suppose I have this C++ program: > > #include > > int main (int argc, char** argv) > > { > > while (1) > > { > > char cmd[80]; > > std::cin.getline(cmd, 80)

Re: [CentOS] [OT] bash here documents

2013-06-24 Thread Steve
m.r...@5-cent.us wrote: > Steve wrote: > > Suppose I have this C++ program: > > #include > > int main (int argc, char** argv) > > { > > while (1) > > { > > char cmd[80]; > > std::cin.getline(cmd, 80); > > std::cout << "response to " << cmd << std::endl; > >

Re: [CentOS] [OT] bash here documents

2013-06-24 Thread Les Mikesell
On Mon, Jun 24, 2013 at 12:36 PM, Steve wrote: > > My junk program is a quick-and-dirty simulation if the actual program I am > trying to use. > I do not have the code for the program and all I know is that it responds to > command input and the only way to terminate it is with . It is somewhat

[CentOS] nvidia-installer

2013-06-24 Thread m . roth
CentOS 6.4 Came back from vacation, rebooted workstation, no X. Wound up running nvidia-installer. Now, I had been using kmod-nvidia, but had to stop a month or so ago, when NVidia stopped supporting my two-yr-old card ("legacy"). When that happened, I uninstalled kmod-nvidia. One dumb question:

Re: [CentOS] Korganizer Calendar Alarms stopped working

2013-06-24 Thread ken
On 06/24/2013 12:42 PM Frank Cox wrote: > On Mon, 24 Jun 2013 12:17:12 -0400 > ken wrote: > >> For a long time--years-- I've been using Korganizer's Calendar. But >> lately-- since the last kernel upgrade, I believe-- the alarms don't >> work anymore. > > Is korganizer calendar alarm the same thin

Re: [CentOS] Korganizer Calendar Alarms stopped working

2013-06-24 Thread Frank Cox
On Mon, 24 Jun 2013 16:07:48 -0400 ken wrote: > So there's still something weird going on, but at > least it's working for the moment and I know to watch for the icon. To make kalarm run every time you log in, you can make sure that it's started and then go your desktop Main Menu - Preferences

Re: [CentOS] Korganizer Calendar Alarms stopped working

2013-06-24 Thread ken
On 06/24/2013 04:27 PM Frank Cox wrote: > On Mon, 24 Jun 2013 16:07:48 -0400 > ken wrote: > >>So there's still something weird going on, but at >> least it's working for the moment and I know to watch for the icon. > > To make kalarm run every time you log in, you can make sure that it's starte

Re: [CentOS] Korganizer Calendar Alarms stopped working

2013-06-24 Thread Frank Cox
On Mon, 24 Jun 2013 17:33:52 -0400 ken wrote: > I don't think that's the problem. kalarm is not currently running > (according to 'ps'), but the KOrganizer daemon is... and most > importantly, korganizer is now properly invoking the alarms (the small > windows are popping up). Then you might w

Re: [CentOS] automatic import of rpm keys

2013-06-24 Thread Markus Falb
On 14.Jun.2013, at 13:20, James Hogarth wrote: > I think I am getting a little confused about these trust things. >> How am *I* supposed to verify the validity of those public keys. >> > > > If you really want to be sure what you should do is compare them from your > system to a trusted source

[CentOS] dmidecode Output

2013-06-24 Thread Mark LaPierre
Hey Y'all, How much can I trust the output of dmidecode? The manual that came with my MB says that my MB can support up to 2 Gb of DDR2 RAM. dmidecode seems tell me that I can load up to 8 Gb on this MB. As 4 Gb DDR2 sticks cost about $100 each I figured maybe I should ask, what's the chances

Re: [CentOS] dmidecode Output

2013-06-24 Thread John R Pierce
On 6/24/2013 5:43 PM, Mark LaPierre wrote: > The manual that came with my MB says that my MB can support up to 2 Gb > of DDR2 RAM. dmidecode seems tell me that I can load up to 8 Gb on this MB. > > As 4 Gb DDR2 sticks cost about $100 each I figured maybe I should ask, > what's the chances that I c

Re: [CentOS] nvidia-installer

2013-06-24 Thread Rob Kampen
On 06/25/2013 07:36 AM, m.r...@5-cent.us wrote: CentOS 6.4 Came back from vacation, rebooted workstation, no X. Wound up running nvidia-installer. Now, I had been using kmod-nvidia, but had to stop a month or so ago, when NVidia stopped supporting my two-yr-old card ("legacy"). When that happene

Re: [CentOS] automatic import of rpm keys

2013-06-24 Thread Rob Kampen
On 06/25/2013 10:38 AM, Markus Falb wrote: On 14.Jun.2013, at 13:20, James Hogarth wrote: I think I am getting a little confused about these trust things. How am *I* supposed to verify the validity of those public keys. If you really want to be sure what you should do is compare them from

Re: [CentOS] LVM + XFS + external log + snapshots - SOLVED

2013-06-24 Thread aurfalien
On Jun 21, 2013, at 2:58 PM, Joseph L. Casale wrote: >> So I have an XFS file system within LVM which has an external log. > >> A snapshot volume is created w/o issue; > >> But when i try to mount the file system; >> mount: /dev/mapper/vg_spock_data-datasnapshot already mounted or /snapshot >

Re: [CentOS] nvidia-installer

2013-06-24 Thread Akemi Yagi
On Mon, Jun 24, 2013 at 6:21 PM, Rob Kampen wrote: > On 06/25/2013 07:36 AM, m.r...@5-cent.us wrote: >> >> CentOS 6.4 >> >> Came back from vacation, rebooted workstation, no X. Wound up running >> nvidia-installer. Now, I had been using kmod-nvidia, but had to stop a >> month or so ago, when NVidi

Re: [CentOS] LVM + XFS + external log + snapshots - SOLVED

2013-06-24 Thread Tru Huynh
On Mon, Jun 24, 2013 at 07:49:21PM -0700, aurfalien wrote: ... > So this worked; > > truncate --size=2G logfile > losetup /dev/loop0 logfile > mount /dev/vg_anette_data/datasnapshot /snapshot -o > logdev=/dev/loop0,nouuid,ro > > Freezing the fs looks to make the log zero. So assigning any devic