On Wed, 2015-03-04 at 15:44 -0700, Pete Travis wrote: > > On Mar 4, 2015 2:25 PM, "Chris Murphy" <lists@xxxxxxxxxxxxxxxxx> > wrote: > > > > On Wed, Mar 4, 2015 at 2:01 PM, Pete Travis <lists@xxxxxxxxxxxxxx> > wrote: > > > > > > > > If cockpit.socket isn't working, yes. > > > > > cockpit.socket is working, and it looks like it starts > cockpit.service > > when I actually go to f22:9090 in a browser; OK false alarm. I > didn't > > realize this was self-starting, maybe that's a new feature. > > > > -- > > Chris Murphy > > -- > > test mailing list > > > I had the same panic moment with F21 server, it isn't new ;) >From what I can see, you both faithfully followed the instructions in: https://fedoraproject.org/wiki/QA:Testcase_Server_cockpit_default#How_to_test so if it's the intention for the cockpit service to be socket-activated (which sounds sane), I guess that that section needs changing or updating accordingly. Any ideas what the text of that testcase *ought* to read? Is there some standard testcase rubric for testing a systemd socket-activated service? Dave -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
