Try radicale, it's in packages.
Il 23/mar/2015 00:42 "L. V. Lammert" ha scritto:
> On Sun, 22 Mar 2015, Jason Crawford wrote:
>
> > I use redmine for project management and that includes a calendar and
> time
> > tracking system.
> >
> Seconded.
>
> Lee
On Sun, 22 Mar 2015, Jason Crawford wrote:
> I use redmine for project management and that includes a calendar and time
> tracking system.
>
Seconded.
Lee
I use redmine for project management and that includes a calendar and time
tracking system.
On Mar 22, 2015 1:44 PM, "Lampshade" wrote:
> What software you use for this purposes?
On Sun, Mar 22, 2015 at 11:03 PM, Jonathan Gray wrote:
> On Sun, Mar 22, 2015 at 06:27:19PM +0100, Mattieu Baptiste wrote:
>> On Sun, Mar 22, 2015 at 2:06 PM, Jonathan Gray wrote:
>> > On Sun, Mar 22, 2015 at 06:49:33AM -0400, Ted Unangst wrote:
>> >> Jonathan Gray wrote:
>> >> > On Sun, Mar 22,
On Sun, Mar 22, 2015 at 06:27:19PM +0100, Mattieu Baptiste wrote:
> On Sun, Mar 22, 2015 at 2:06 PM, Jonathan Gray wrote:
> > On Sun, Mar 22, 2015 at 06:49:33AM -0400, Ted Unangst wrote:
> >> Jonathan Gray wrote:
> >> > On Sun, Mar 22, 2015 at 09:16:08AM +0100, Stefan Sperling wrote:
> >> > >
> >>
Kevin Chadwick wrote:
> So I could renice the processes cron runs but decided to renice the
> whole of cron instead/as well.
>
> I therefore added a renice line to rc.local but rc.local runs before
> cron. What is the best way to do this... add a line to edit the daemon
> line in /etc/rc.d/cron as
Lampshade writes:
> What software you use for this purposes?
I use GNU Emacs with org-mode. Emacs is included in OpenBSD packages.
So I could renice the processes cron runs but decided to renice the
whole of cron instead/as well.
I therefore added a renice line to rc.local but rc.local runs before
cron. What is the best way to do this... add a line to edit the daemon
line in /etc/rc.d/cron as needed on startup?
Or did I see
Hi,
Lampshade wrote on Sun, Mar 22, 2015 at 04:56:18PM +0100:
> What software you use for this purposes?
when(1), see the productivity/when port.
Yours,
Ingo
On Sat, 21 Mar 2015 11:26:39 + (UTC)
Stuart Henderson wrote:
> On 2015-03-21, Riccardo Mottola wrote:
> > Hi,
> >
> > Brian McCafferty wrote:
> >> Just a serial cable, then you can use tip(1). The connections and
> >> other info are in the V120 user guide which you can download from
> >> Or
What software you use for this purposes?
On Sun, Mar 22, 2015 at 2:06 PM, Jonathan Gray wrote:
> On Sun, Mar 22, 2015 at 06:49:33AM -0400, Ted Unangst wrote:
>> Jonathan Gray wrote:
>> > On Sun, Mar 22, 2015 at 09:16:08AM +0100, Stefan Sperling wrote:
>> > >
>> > > If the firmare image is not present at boot, no interface is created.
>>
On Sun, Mar 22, 2015 at 03:26:30PM +, Stuart Henderson wrote:
> On 2015-03-22, T. Ribbrock wrote:
> > What I cannot seem to get to work is that sensorsd *reacts* to these
> > changes. Based on the examples in the thread mentioned above, I've
> > created a small script "/etc/sensorsd/upd.sh" th
On 2015-03-22, T. Ribbrock wrote:
> What I cannot seem to get to work is that sensorsd *reacts* to these
> changes. Based on the examples in the thread mentioned above, I've
> created a small script "/etc/sensorsd/upd.sh" that looks as follows:
>
> # cat /etc/sensorsd/upd.sh
> echo "${@}" | logge
On Sat, 21 Mar 2015 14:14:22 -0700
luke...@onemodel.org wrote:
> Thanks to all who've commented: this has been educational & useful.
Systrace is also an option but the policy writing could be a little
work, the regex support is certainly helpful there.
systrace -A is very helpful
then edit files
Hi all,
one of the remaining "kinks in the cable" that still need working out
after me updating to OpenBSD 5.6 is the fact that I can no longer use
apcupsd to monitor the "APC Back-UPS CS 500" that is connected to the
server via USB. From what I have gathered so far, one has to use
sensorsd instea
On Sun, Mar 22, 2015 at 06:49:33AM -0400, Ted Unangst wrote:
> Jonathan Gray wrote:
> > On Sun, Mar 22, 2015 at 09:16:08AM +0100, Stefan Sperling wrote:
> > >
> > > If the firmare image is not present at boot, no interface is created.
> > > After installing the firmware with fw_update (which succe
It does the same thing on 5.3 through -current. I haven't put that box in the
rack yet so I can try a few older kernels too and see if any work.
Will report back.
> On Mar 22, 2015, at 8:45 AM, Claudio Jeker wrote:
>
>> On Sun, Mar 22, 2015 at 09:53:24AM +, Stuart Henderson wrote:
>>> On
On Sun, Mar 22, 2015 at 09:53:24AM +, Stuart Henderson wrote:
> On 2015-03-21, John E.P. Hynes wrote:
> > If anyone has any ideas, or would like more info, or if a dev suspects
> > it could be the driver, contact me off-list and I can arrange to send
> > hardware if it helps.
>
> It might b
On Sun, Mar 22, 2015 at 10:49 AM, Stuart Henderson wrote:
> Untested, but maybe this works:
>
> ifconfig em0 up
> ifconfig iwm0 up
> ifconfig trunk0 create
> ifconfig trunk0 trunkport iwm0 trunkport em0 trunkproto failover
> ifconfig trunk0 -trunkport iwm0
> ifconfig iwm0 up
> ifconfig trunk0 trun
Jonathan Gray wrote:
> On Sun, Mar 22, 2015 at 09:16:08AM +0100, Stefan Sperling wrote:
> >
> > If the firmare image is not present at boot, no interface is created.
> > After installing the firmware with fw_update (which succeeds because
> > it looks for "iwm" in dmesg not ifconfig) there is no w
On 2015-03-21, John E.P. Hynes wrote:
> If anyone has any ideas, or would like more info, or if a dev suspects
> it could be the driver, contact me off-list and I can arrange to send
> hardware if it helps.
It might be worth talking to Supermicro.
On 2015-03-22, Ted Unangst wrote:
> trunk uses the MAC of the master device, which is probably going to be em0 in
> many setups, but it's possible to reorder the devices and make iwm0 the
> master. A little less convenient as it won't failover to the ethernet
> automatically.
Untested, but maybe
On Sun, Mar 22, 2015 at 09:16:08AM +0100, Stefan Sperling wrote:
> On Sun, Mar 22, 2015 at 01:45:45PM +1100, Jonathan Gray wrote:
> > Try the following.
>
> This diff re-introduces an unrelated problem fixed in r1.7.
>
> Interface attachment is moved back to the attach-hook, and the driver
> trie
On Sun, Mar 22, 2015 at 01:45:45PM +1100, Jonathan Gray wrote:
> Try the following.
This diff re-introduces an unrelated problem fixed in r1.7.
Interface attachment is moved back to the attach-hook, and the driver
tries to load the firmware from disk before creating an interface.
If the firmare
25 matches
Mail list logo
